Difference between revisions of "UNAUTOMATABLE TEST CASES"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................") |
|||
| Line 15: | Line 15: | ||
<span style="font-family: Arial; font-size: 16px">Most recommended:</span><br /> | <span style="font-family: Arial; font-size: 16px">Most recommended:</span><br /> | ||
| − | * <span style="font-family: Arial; font-size: 16px">[[ | + | * <span style="font-family: Arial; font-size: 16px">[[SHARE INFORMATION]]: apply this pattern to clear misunderstandings between testers and automators</span> |
* <span style="font-family: Arial; font-size: 16px">[[WHOLE TEAM APPROACH]]: apply this pattern to get rid of misunderstandings in the team</span> | * <span style="font-family: Arial; font-size: 16px">[[WHOLE TEAM APPROACH]]: apply this pattern to get rid of misunderstandings in the team</span> | ||
| − | * <span style="font-size: 16px">[[ | + | * <span style="font-size: 16px">[[THINK OUT-OF-THE-BOX]]: try to look at the problem from unusual viewpoints</span> |
<br /> <span style="font-family: Arial; font-size: 16px">Other useful patterns:</span><br /> | <br /> <span style="font-family: Arial; font-size: 16px">Other useful patterns:</span><br /> | ||
* <span style="font-size: 16px">[[ KNOW WHEN TO STOP]]: this pattern helps to recognize that not all tests are automatable</span> | * <span style="font-size: 16px">[[ KNOW WHEN TO STOP]]: this pattern helps to recognize that not all tests are automatable</span> | ||
* <span style="font-size: 16px">[[MANAGEMENT SUPPORT]]: you will need to use this pattern especially if you want to implement a [[WHOLE TEAM APPROACH]] and nobody is going agile yet in your company</span> | * <span style="font-size: 16px">[[MANAGEMENT SUPPORT]]: you will need to use this pattern especially if you want to implement a [[WHOLE TEAM APPROACH]] and nobody is going agile yet in your company</span> | ||
| − | * <span style="font-family: Arial; font-size: 16px">[[ | + | * <span style="font-family: Arial; font-size: 16px">[[PAIR UP]]: apply this pattern to enhance communication and learning between testers and automators</span> |
<br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Design Issues]] / Back to [[Test Automation Issues]]</span></div> | <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Design Issues]] / Back to [[Test Automation Issues]]</span></div> | ||
Revision as of 15:31, 4 April 2018
.................................................................................................................Main Page / Back to Design Issues / Back to Test Automation Issues
.................................................................................................................Main Page / Back to Design Issues / Back to Test Automation Issues
Issue summary
Existing test cases are “unautomatable”
Category
Design
Examples
- Test cases are written in a very "terse" way assuming that manual testers know the SUT inside out. Automators usually cannot understand what they are supposed to automate.
- Test cases build on each other to complex scenarios that make it very difficult to write test cases independent from each other
- Test cases are performed only once in a while and are quite complicated
Questions
Who writes the test cases?
Has time been planned to explain the test cases to the automation team?
Resolving Patterns
Most recommended:
- SHARE INFORMATION: apply this pattern to clear misunderstandings between testers and automators
- WHOLE TEAM APPROACH: apply this pattern to get rid of misunderstandings in the team
- THINK OUT-OF-THE-BOX: try to look at the problem from unusual viewpoints
Other useful patterns:
- KNOW WHEN TO STOP: this pattern helps to recognize that not all tests are automatable
- MANAGEMENT SUPPORT: you will need to use this pattern especially if you want to implement a WHOLE TEAM APPROACH and nobody is going agile yet in your company
- PAIR UP: apply this pattern to enhance communication and learning between testers and automators
.................................................................................................................Main Page / Back to Design Issues / Back to Test Automation Issues