Quality Assurance EngineerJob Shadow Day, April 11, 2014

About me:5 days of the week:!• Junior Quality Assurance Engineer !

Day by day:!• full-time Mozilla Rep • full-time Romanian Mozilla Community

member • full-time Firefox user • part-time Firefox OS app reviewer • part-time QA contributor !

Where you can find me:!• twitter: @andreea_popescu • LinkedIn: @andreeazpopescu

What a QA engineer does!

• Writes test plans from the requirements, specifications and test strategies

• Uses versioning systems to code test scripts

• Creates and perform test campaign whenever it is necessary to fit in the overall planning

• Uses bug tracking database to report bugs

• Analyses test results

• Reports results to the QA manager

• Raises an alert when an important issue is likely to put in jeopardy the whole project

•

What makes a good QA Engineer

1. Broad understanding of the product

• The QA engineer must know the

product well enough

• Knowing the product includes also

knowing how end-users expect it

to work

• The QA engineer must have a

"customer-focus" vision

2. Effective communication• Direct communication with both

Development and Product teams

• Capability to communicate with technical and non-technical people

• Having the diplomacy to say "no" when a bug is considered as not fixed

• Having the diplomacy to communicate about a bug without “offending" the developer

3. Creativity

• The QA engineer must use its creativity to figure out all the scenarios that are likely to detect a bug

• The QA engineer must be able to "see beyond the obvious”.

4. Development knowledge

• Development capabilities are required to eventually code automated tests

• If you know how to develop, you have better ideas on what is "dangerous" to code, so what to test more thoroughly

QA Engineer at XWiki

1. Manual testing

test.xwiki.org

hall of fame

2. Reporting bugs

• A bug can be: blocker, critical,

major, minor or trivial.

• Jira - for bug tracking

• We can come, also, with New

Features, Ideas and Improvements.

3. Bugs

• translation bugs

• design bugs

• functionality bugs

• security bugs

• navigation bugs

• other bugs

The end.

Sources:

• [1] - http://www.xqual.com/documentation/tutorial_qa_engineer_skills.html (content)!

• [2] - http://geek-and-poke.com (images)