Tester personas


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Tester personas

  1. 1. The many aspects of a tester
  2. 2. Introduction <ul><li>A perfect tester has to not only be an excellent developer, but also have great domain knowledge, understanding of test tools, ability to present risks and results, great understanding of test management, deep knowledge of test techniques and methods, and much more </li></ul><ul><li>Impossible to find such a person </li></ul><ul><li>Many different types of testers </li></ul><ul><li>Each type of tester prioritizes different skills and abilities </li></ul><ul><li>Each type must be used in the right way to maximize potential </li></ul><ul><li>In this presentation, a number of types are presented, but testers could be categorized in many other ways </li></ul>
  3. 3. Personas Overview E2E Tester System Tester Domain Tester Developer in Test Verification Tool Engineer Test Automation Engineer
  4. 4. Developer in Test <ul><li>Work Description </li></ul><ul><ul><li>Work side-by-side with developers enabling the team to produce high quality code by writing unit/API test cases in C and Java during feature development </li></ul></ul><ul><ul><li>Driving not only functional quality, but also performance, stability, power consumption and similar during design & development phase </li></ul></ul><ul><ul><li>Pushing for testability and maintainability of the code to enable testing </li></ul></ul><ul><ul><li>Support developers with expertise in their unit testing effort </li></ul></ul><ul><li>Key Competencies in priority </li></ul><ul><ul><li>C & Java competence </li></ul></ul><ul><ul><li>Test competence </li></ul></ul><ul><ul><li>Driving testability </li></ul></ul><ul><ul><li>Domain knowledge </li></ul></ul>
  5. 5. Verification Tool Engineer <ul><li>Work Description </li></ul><ul><ul><li>Push testing downstream by continuously working with new tools to enable testing early </li></ul></ul><ul><ul><li>Put requirements on the development line organization what is needed to increase testability of the code </li></ul></ul><ul><ul><li>Drive development of new verification tools </li></ul></ul><ul><ul><li>Roll out new tools in the organization </li></ul></ul><ul><ul><li>Usually works alone or in pairs, but interfacing a lot of testers and developers </li></ul></ul><ul><li>Key Competencies in priority </li></ul><ul><ul><li>Verification & Development tools knowledge </li></ul></ul><ul><ul><li>Driving testability </li></ul></ul><ul><ul><li>Java & C & Script competence </li></ul></ul><ul><ul><li>Test Competence </li></ul></ul>
  6. 6. Test Automation Engineer <ul><li>Work Description </li></ul><ul><ul><li>Develop system API tests which cover the gaps left by the Developers in Test </li></ul></ul><ul><ul><li>To continuously executed and monitor automated test cases and analyze the results </li></ul></ul><ul><ul><li>Push requirements on verification tool engineers for new tools </li></ul></ul><ul><ul><li>Works in a small team of dedicated automation experts, as part of an automated test lab </li></ul></ul><ul><li>Key Competencies in priority </li></ul><ul><ul><li>C & Java competence </li></ul></ul><ul><ul><li>Test competence </li></ul></ul><ul><ul><li>Domain knowledge </li></ul></ul><ul><ul><li>Verification tool knowledge </li></ul></ul>
  7. 7. Domain Tester <ul><li>Work Description </li></ul><ul><ul><li>Is an expert on a domain, such as local connectivity, graphics, device drivers, or similar </li></ul></ul><ul><ul><li>Focuses on tool-aided manual testing </li></ul></ul><ul><ul><li>Can work both in teams with developers, or in dedicated test teams, depending on the assignment </li></ul></ul><ul><ul><li>Support new development with requirements from a verification perspective </li></ul></ul><ul><ul><li>Write and execute manual acceptance tests for features in development </li></ul></ul><ul><ul><li>Execute manual tests and exploratory testing charters on the software main branch to report status and find defects </li></ul></ul><ul><li>Key Competencies in priority </li></ul><ul><ul><li>Test competence (including exploratory testing) </li></ul></ul><ul><ul><li>Domain knowledge </li></ul></ul><ul><ul><li>Verification tool knowledge </li></ul></ul><ul><ul><li>Requirements competence </li></ul></ul>
  8. 8. System Tester <ul><li>Work Description </li></ul><ul><ul><li>Focuses on the system instead of a specific domain </li></ul></ul><ul><ul><li>Working mostly in dedicated test teams, further away from development </li></ul></ul><ul><ul><li>Focus on other aspects than pure functionality; system performance, system stability, system interactions and so on </li></ul></ul><ul><ul><li>Mostly executes exploratory charters to cover as much of the system as possible with the least effort </li></ul></ul><ul><ul><li>Measures system KPIs to evaluate the quality of the system, often using verification tools </li></ul></ul><ul><ul><li>Put requirements on the system which are needed for verification </li></ul></ul><ul><li>Key Competencies in priority </li></ul><ul><ul><li>Test competence (focus on exploratory testing) </li></ul></ul><ul><ul><li>System knowledge </li></ul></ul><ul><ul><li>System requirements competence </li></ul></ul><ul><ul><li>Verification tools knowledge </li></ul></ul>
  9. 9. E2E Tester <ul><li>Work Description </li></ul><ul><ul><li>Works with the final product that ships to customers </li></ul></ul><ul><ul><li>Understands the customers needs and requirements </li></ul></ul><ul><ul><li>Focus on using the product the same way as the customer – mostly manual testing </li></ul></ul><ul><ul><li>Working in dedicated test team with close connection to customer interfaces </li></ul></ul><ul><ul><li>Must understand how the different domains and the system work to be able to test from an E2E perspective without mistaking design decisions for defects </li></ul></ul><ul><li>Key Competencies in priority </li></ul><ul><ul><li>Test competence (focus on exploratory testing) </li></ul></ul><ul><ul><li>Customer focus </li></ul></ul><ul><ul><li>Customer requirements competence </li></ul></ul><ul><ul><li>System & Domain knowledge </li></ul></ul>
  10. 10. Q&A <ul><li>Where is our organization today? </li></ul><ul><ul><li>What roles dominate? </li></ul></ul><ul><ul><li>Pie-chart which shows how many testers of each role we have? </li></ul></ul><ul><li>What is our goal? </li></ul><ul><ul><li>What roles do we want in our organization? </li></ul></ul><ul><ul><li>Ratio between the different types of testers </li></ul></ul><ul><li>Are there any more roles than the six described in this presentation? </li></ul><ul><li>How do we get to the new ratio between testers if we are not there today? </li></ul>
  11. 11. References Material <ul><li>[1] Career Paths for Testers Using Personas </li></ul><ul><li>http://www.stickyminds.com/s.asp?F=S16548_COL_2 </li></ul>