General issues are the issues that one feels when test automation is not going as expected, but one cannot really pinpoint a specific problem, because usually more then one are causing the pain. Note that in order to help you when you are just beginning with test automation, we have added here the issue NO PREVIOUS TEST AUTOMATION, that is actually a management issue.
These are the steps to take in order to pinpoint the most pressing issue to be solved:
  1. Select the general issue that best describes the most pressing problem in your test automation.
  2. Examine what kind of issues can cause it (probably more than one).
  3. Select the one that you deem most pressing.
  4. Repeat steps 2. and 3. until you reach the specific issue that needs to be solved first. It will suggest the patterns needed to solve it.
  5. Select the pattern(s) that best fit your context and apply it/them.
  6. If you still have problems, start again from step 1.

Issue
Description
EXPECTATIONS NOT MET
Test automation is not meeting the expectations of managers, testers or developers
NO PREVIOUS TEST AUTOMATION
You are just starting with automation and have never done it before
NO DIRECTION
Test automation is stumbling along with no specific goal or no clear strategy
MISSING RESOURCES
Test automation is being hinderd by lack of automators, testers, tools, hardware etc.
MISSING KNOWLEDGE
Automators or testers don't know how to do good automation, how to use the tools, have limited experience in the SUT or new team members take too long to become productive
MISSING SUPPORT
Test automation is not supported by managers, testers or developers

Note: the issues are presented in alphabetical order, NOT in order of importance.

The Test Automation General Issues Mind Map shows an overview of the General Issues.


Home

Back to Test Automation Issues

Forward to Process Issues