FIVE MISTAKES MOST QA ENGINEERS DO

Alexander KuznyakCiklum Technologies

or “Being a QA in not only about technical skills”

POINTS TO DISCUSS:

• “GOOD QA ENGINEER” PORTRAITLETS CREATE IT TOGETHER

• WHY EACH AND EVERY QA IS NOT THAT “GOOD”?FIVE COMMON CASES FROM MY PRACTICE AND HOW TO DEAL WITH EACH OF THEM

• DO YOU PLAN TO BECOME BETTER?DISCUSSION SUMMARY AND MY SUGGESTIONS

“GOOD QA ENGINEER” PORTRAITLETS CREATE IT TOGETHER

OFTEN MADE

MISTAKES

WHAT IS CLEAR FOR ME, IS CLEAR FOR EVERYBODYLACK OF COMMUNICATION SKILLS, ENGLISH LEVEL, ETC.

WE NEED TO FIX ALL BUGS BEFORE RELEASE

LACK OF BUSINESS VALUE FOCUS, MISUNDERSTANDING PROJECT GOALS

WE NEED TO AUTOMATE EVERYTHING

MISUNDERSTANDING AUTOMATION NECESSITY AND GOALS

QA DOCUMENTATION IS F*ING IMPORTANT!!!

PUTTING TOOLS AND INSTRUMENTS HIGHER TO PROJECT ITSELF

MY TECH. LEVEL, ENGLISH, ETC. ARE PERFECT

OVERESTIMATING OWN SKILLS, INABILITY TO PERCEIVE CONSTRUCTIVE CRITICISM

AND THERE IS MORE…

• MAKE YOUR DELIVERABLES GOOD FOR OTHERS, NOT ONLY FOR YOU 1

• ASK “WHY?” AND “WHAT PROBLEMS I WILL SOLVE?” BEFORE DOING SOMETHING

2• LEARN YOUR PRODUCT GOALS AND PAY

ATTENTION TO MARKET TRENDS3• YOU ARE NOT PERFECT AND LIKELY WILL

NEVER BE. LIVE WITH THIS 4• SET GOALS, CHECK HOW YOU STICK TO

THE PLAN5

HOW TO AVOID OR MINIMIZE STUFF WRITTEN ABOVE?

QA-ING YOURSELF AS A METHOD OF GETTING BETTER

• COMMUNICATION

SKILLS

• IMPROVE ENGLISH

• BE PROACTIVE

• BE A TEAM PLAYER

• ASK FOR FEEDBACK

THANK YOUQUESTIONS?