Difference between revisions of "Test Manager"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 16px">The most important thing to learn about test automation is the difference between mana...") |
|||
| Line 18: | Line 18: | ||
* <span style="font-size: 16px">recruiting and training test automators ([[AUTOMATION ROLES]], [[GET TRAINING]])</span> | * <span style="font-size: 16px">recruiting and training test automators ([[AUTOMATION ROLES]], [[GET TRAINING]])</span> | ||
* <span style="font-size: 16px">getting [[MANAGEMENT SUPPORT]] for test automation by communicating with management, testers and development ([[SHARE INFORMATION]], [[CELEBRATE SUCCESS]], [[SELL THE BENEFITS]])</span> | * <span style="font-size: 16px">getting [[MANAGEMENT SUPPORT]] for test automation by communicating with management, testers and development ([[SHARE INFORMATION]], [[CELEBRATE SUCCESS]], [[SELL THE BENEFITS]])</span> | ||
| − | <br /> <br /> <span style="font-size: 16px">[[Back]]</span></div> | + | <br /> <br /> <span style="font-size: 16px">[[LIMITED EXPERIENCE | Back]]</span></div> |
Revision as of 13:22, 24 April 2018
The most important thing to learn about test automation is the difference between managing testing and test automation
A test manager is responsible for:
Back
A test manager is responsible for:
- the master test plan
- defining standards and processes
- developing the specific test plans and having them performed
- giving information about the test status (how many tests have been executed? how many bugs have been found (and how serious)? how many have been corrected (or not)? how much time and resources are needed? etc.)
- helping decide if the application is ready for release
- recruiting and training testers
A test manager in charge of test automation is also responsible for:
- defining the scope of test automation (SET CLEAR GOALS, DO A PILOT)
- defining standards and processes for test automation ([ STANDARDS]], GOOD DEVELOPMENT PROCESS)
- defining the strategy for test automation (TESTWARE ARCHITECTURE, ABSTRACTION LEVELS, MAINTAINABLE TESTWARE)
- deciding what to automate and what not (AUTOMATE WHAT'S NEEDED, KNOW WHEN TO STOP)
- provide the resources, people, machines and tools (DEDICATED RESOURCES, DEPUTY, RIGHT TOOLS, PLAN SUPPORT ACTIVITIES)
- planning development and maintainance of test automation (SHORT ITERATIONS, WHOLE TEAM APPROACH, MAINTAIN THE TESTWARE, REFACTOR THE TESTWARE)
- having the automated tests executed, eventually selecting an appropriate subset to run (UNATTENDED TEST EXECUTION, PRIORITIZE TESTS, TEST SELECTOR)
- recruiting and training test automators (AUTOMATION ROLES, GET TRAINING)
- getting MANAGEMENT SUPPORT for test automation by communicating with management, testers and development (SHARE INFORMATION, CELEBRATE SUCCESS, SELL THE BENEFITS)
Back