Difference between revisions of "LIMITED EXPERIENCE"
Jump to navigation
Jump to search
m (Removed link to general issues) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | <div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Issues]] / Back to [[Test Automation Issues]]</span | + | <div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Issues]] / Back to [[Test Automation Issues]]</span> |
=<span style="font-family: Arial; font-size: 16px">'''Issue summary'''</span>= | =<span style="font-family: Arial; font-size: 16px">'''Issue summary'''</span>= | ||
| − | <span style="font-family: Arial; font-size: 16px">The test automation team has limited experience in test automation or in the SUT or new team members take too long to become productive</span | + | <span style="font-family: Arial; font-size: 16px">The test automation team has limited experience in test automation or in the SUT or new team members take too long to become productive</span> |
=<span style="font-family: Arial; font-size: 16px">'''Category'''</span>= | =<span style="font-family: Arial; font-size: 16px">'''Category'''</span>= | ||
| − | <span style="font-family: Arial; font-size: 16px">Management</span | + | <span style="font-family: Arial; font-size: 16px">Management</span><br /> |
=<span style="font-family: Arial; font-size: 16px">'''Examples'''</span>= | =<span style="font-family: Arial; font-size: 16px">'''Examples'''</span>= | ||
| − | |||
| − | |||
# <span style="font-family: Arial; font-size: 16px">Test automation is planned, but nobody in the company has done it yet</span> | # <span style="font-family: Arial; font-size: 16px">Test automation is planned, but nobody in the company has done it yet</span> | ||
# <span style="font-family: Arial; font-size: 16px">Only one person on the team knows the test tool</span> | # <span style="font-family: Arial; font-size: 16px">Only one person on the team knows the test tool</span> | ||
| Line 14: | Line 12: | ||
# <span style="font-family: Arial; font-size: 16px">Current team members don't have time to coach newcomers</span> | # <span style="font-family: Arial; font-size: 16px">Current team members don't have time to coach newcomers</span> | ||
# <span style="font-family: Arial; font-size: 16px">Testers don't know how to write test cases for automation</span> | # <span style="font-family: Arial; font-size: 16px">Testers don't know how to write test cases for automation</span> | ||
| − | |||
=<span style="font-family: Arial; font-size: 16px">'''Questions'''</span>= | =<span style="font-family: Arial; font-size: 16px">'''Questions'''</span>= | ||
| − | <span style="font-family: Arial; font-size: 16px">Who is doing the automation? Testers? Developers?</span><br /> <span style="font-family: Arial; font-size: 16px">Has the tool been selected by the automation team? Or is it shelfware and should be resuscitated?</span><br /> <span style="font-family: Arial; font-size: 16px">Does the tool vendor offer trainings? Are the help manuals adequate? Are the help manuals in the current language?</span><br /> <span style="font-family: Arial; font-size: 16px">Is the SUT adequately documented?</span><br /> <span style="font-family: Arial; font-size: 16px">Is there a budget for training?</span | + | <span style="font-family: Arial; font-size: 16px">Who is doing the automation? Testers? Developers?</span><br /> <span style="font-family: Arial; font-size: 16px">Has the tool been selected by the automation team? Or is it shelfware and should be resuscitated?</span><br /> <span style="font-family: Arial; font-size: 16px">Does the tool vendor offer trainings? Are the help manuals adequate? Are the help manuals in the current language?</span><br /> <span style="font-family: Arial; font-size: 16px">Is the SUT adequately documented?</span><br /> <span style="font-family: Arial; font-size: 16px">Is there a budget for training?</span> |
=<span style="font-family: Arial; font-size: 16px">'''Resolving Patterns'''</span>= | =<span style="font-family: Arial; font-size: 16px">'''Resolving Patterns'''</span>= | ||
| − | + | <span style="font-size: 16px">Depending on your previous experiences you should first look up the patterns suggested here:</span><br /> | |
| − | |||
* <span style="font-size: 16px">[[Tester]]</span> | * <span style="font-size: 16px">[[Tester]]</span> | ||
* <span style="font-size: 16px">[[Developer]]</span> | * <span style="font-size: 16px">[[Developer]]</span> | ||
* <span style="font-size: 16px">[[Test Manager]]</span> | * <span style="font-size: 16px">[[Test Manager]]</span> | ||
| − | + | <br /> <span style="font-family: Arial; font-size: 16px">Most recommended:</span><br /> | |
| − | |||
* <span style="font-size: 16px">[[CHECK-TO-LEARN]]: Let new team members learn by checking the health of the existing automation testware</span> | * <span style="font-size: 16px">[[CHECK-TO-LEARN]]: Let new team members learn by checking the health of the existing automation testware</span> | ||
* <span style="font-size: 16px">[[DOCUMENT THE TESTWARE]]: Use this pattern from the very beginning of the automation effort</span> | * <span style="font-size: 16px">[[DOCUMENT THE TESTWARE]]: Use this pattern from the very beginning of the automation effort</span> | ||
| Line 31: | Line 26: | ||
* <span style="font-size: 16px">[[ASK FOR HELP]]: This pattern is a no-brainer! Use it</span> | * <span style="font-size: 16px">[[ASK FOR HELP]]: This pattern is a no-brainer! Use it</span> | ||
<br /> <span style="font-size: 16px">Other useful patterns:</span><br /> | <br /> <span style="font-size: 16px">Other useful patterns:</span><br /> | ||
| − | |||
* <span style="font-family: Arial; font-size: 16px">[[PAIR UP]]: This is the pattern of choice when newbies are supposed to integrate into the team as fast as possible</span> | * <span style="font-family: Arial; font-size: 16px">[[PAIR UP]]: This is the pattern of choice when newbies are supposed to integrate into the team as fast as possible</span> | ||
* <span style="font-size: 16px">[[TAKE SMALL STEPS]]: Use this pattern to learn, you don't have to build Rome in one day </span> | * <span style="font-size: 16px">[[TAKE SMALL STEPS]]: Use this pattern to learn, you don't have to build Rome in one day </span> | ||
* <span style="font-size: 16px">[[STEEL THREAD]]: Good pattern for learning to navigate test automation through the SUT</span> | * <span style="font-size: 16px">[[STEEL THREAD]]: Good pattern for learning to navigate test automation through the SUT</span> | ||
* <span style="font-size: 16px">[[PREFER FAMILIAR SOLUTIONS]]: use this pattern if team members already use tools or processes that can be applied succesfully also to the test automation project</span> | * <span style="font-size: 16px">[[PREFER FAMILIAR SOLUTIONS]]: use this pattern if team members already use tools or processes that can be applied succesfully also to the test automation project</span> | ||
| − | <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management | + | <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Issues]] / Back to [[Test Automation Issues]]</span></div> |
Latest revision as of 17:08, 2 July 2018
.................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues
.................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues
Issue summary
The test automation team has limited experience in test automation or in the SUT or new team members take too long to become productive
Category
Management
Examples
- Test automation is planned, but nobody in the company has done it yet
- Only one person on the team knows the test tool
- Test automators know the tool, but not the SUT
- A new tool has been acquired
- New team members find it difficult to learn how to use the test tool.
- Current team members don't have time to coach newcomers
- Testers don't know how to write test cases for automation
Questions
Who is doing the automation? Testers? Developers?
Has the tool been selected by the automation team? Or is it shelfware and should be resuscitated?
Does the tool vendor offer trainings? Are the help manuals adequate? Are the help manuals in the current language?
Is the SUT adequately documented?
Is there a budget for training?
Resolving Patterns
Depending on your previous experiences you should first look up the patterns suggested here:
Most recommended:
- CHECK-TO-LEARN: Let new team members learn by checking the health of the existing automation testware
- DOCUMENT THE TESTWARE: Use this pattern from the very beginning of the automation effort
- DO A PILOT: use this pattern when the automation effort is starting, so that team members can learn hands on
- GET TRAINING: this pattern is the right choice after tools and architecture have been selected, but also for testers to learn how to write test cases suitable for automation
- ASK FOR HELP: This pattern is a no-brainer! Use it
Other useful patterns:
- PAIR UP: This is the pattern of choice when newbies are supposed to integrate into the team as fast as possible
- TAKE SMALL STEPS: Use this pattern to learn, you don't have to build Rome in one day
- STEEL THREAD: Good pattern for learning to navigate test automation through the SUT
- PREFER FAMILIAR SOLUTIONS: use this pattern if team members already use tools or processes that can be applied succesfully also to the test automation project
.................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues