LIMITED EXPERIENCE

From Test Automation Patterns
Revision as of 14:12, 28 April 2018 by Seretta (talk | contribs) (Topic titles in capital letters)
Jump to navigation Jump to search
.................................................................................................................Main Page / Back to Management Issues / Back to General 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

  1. Test automation is planned, but nobody in the company has done it yet
  2. Only one person on the team knows the test tool
  3. Test automators know the tool, but not the SUT
  4. A new tool has been acquired
  5. New team members find it difficult to learn how to use the test tool.
  6. Current team members don't have time to coach newcomers
  7. 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 General Issues / Back to Test Automation Issues