Difference between revisions of "NON-TECHNICAL-TESTERS"
Jump to navigation
Jump to search
m (Topic titles in capital letters) |
m (empty lines removed) |
||
| Line 1: | Line 1: | ||
<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Process 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 [[Process Issues]] / Back to [[Test Automation Issues]]</span> | ||
=<span style="font-size: 16px">'''Issue summary'''</span>= | =<span style="font-size: 16px">'''Issue summary'''</span>= | ||
| − | + | <span style="font-size: 16px">Testers aren’t able to write automation test cases if they are not adept with the automation tools. </span> | |
=<span style="font-size: 16px">'''Category'''</span>= | =<span style="font-size: 16px">'''Category'''</span>= | ||
| − | + | <span style="font-size: 16px">Process</span><br /> | |
=<span style="font-size: 16px">'''Examples'''</span>= | =<span style="font-size: 16px">'''Examples'''</span>= | ||
| − | |||
| − | |||
# <span style="font-size: 16px">Testers are interested in testing and not all testers want to learn the scripting languages of different automation tools. On the other hand automators aren't necessarily well aquainted with the application, so there are often communication problems.</span> | # <span style="font-size: 16px">Testers are interested in testing and not all testers want to learn the scripting languages of different automation tools. On the other hand automators aren't necessarily well aquainted with the application, so there are often communication problems.</span> | ||
# <span style="font-size: 16px">Testers can prepare test cases from the requirements and can therefore start even before the application has been developed. Automators must usually wait for at least a rudimentary GUI.</span> | # <span style="font-size: 16px">Testers can prepare test cases from the requirements and can therefore start even before the application has been developed. Automators must usually wait for at least a rudimentary GUI.</span> | ||
=<span style="font-size: 16px">'''Resolving Patterns'''</span>= | =<span style="font-size: 16px">'''Resolving Patterns'''</span>= | ||
| − | + | <span style="font-size: 16px">Most recommended:</span><br /> | |
| − | |||
* <span style="font-size: 16px">[[DOMAIN-DRIVEN TESTING]]: Apply this pattern to get rid of this issue for sure. It helps you find the best architecture when the testers cannot also be automators </span> | * <span style="font-size: 16px">[[DOMAIN-DRIVEN TESTING]]: Apply this pattern to get rid of this issue for sure. It helps you find the best architecture when the testers cannot also be automators </span> | ||
* <span style="font-size: 16px"><span style="font-size: 16px">[[OBJECT MAP]]</span>: This pattern is useful even if you don't implement [[DOMAIN-DRIVEN TESTING]] because it forces the development of more readable scripts</span> | * <span style="font-size: 16px"><span style="font-size: 16px">[[OBJECT MAP]]</span>: This pattern is useful even if you don't implement [[DOMAIN-DRIVEN TESTING]] because it forces the development of more readable scripts</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-size: 16px">[[KEYWORD-DRIVEN TESTING]]: This pattern is widely used already, so it will be not only easy to apply for your testers, but you will also find it easier to find automators able to implement it</span> | * <span style="font-size: 16px">[[KEYWORD-DRIVEN TESTING]]: This pattern is widely used already, so it will be not only easy to apply for your testers, but you will also find it easier to find automators able to implement it</span> | ||
* <span style="font-size: 16px">[[SHARE INFORMATION]]: If you have issues like Example 1. this is the pattern for you!</span> | * <span style="font-size: 16px">[[SHARE INFORMATION]]: If you have issues like Example 1. this is the pattern for you!</span> | ||
* <span style="font-size: 16px">[[TEST AUTOMATION FRAMEWORK]]: If you plan to implement [[DOMAIN-DRIVEN TESTING]] you will need this pattern too. Even if you don't, this pattern can make it easier for testers to use and help implement the automation</span> | * <span style="font-size: 16px">[[TEST AUTOMATION FRAMEWORK]]: If you plan to implement [[DOMAIN-DRIVEN TESTING]] you will need this pattern too. Even if you don't, this pattern can make it easier for testers to use and help implement the automation</span> | ||
| − | + | <br /> <span style="font-size: 16px">The [[NON-TECHNICAL-TESTERS%20Mind%20Map]] shows how the resolving patterns relate to other patterns.</span><br /> <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Process Issues]] / Back to [[Test Automation Issues]]</span><br /> <span style="font-size: 14px">B2</span></div> | |
Revision as of 06:38, 5 May 2018
.................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues
The NON-TECHNICAL-TESTERS Mind Map shows how the resolving patterns relate to other patterns.
.................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues
B2
Issue summary
Testers aren’t able to write automation test cases if they are not adept with the automation tools.
Category
Process
Examples
- Testers are interested in testing and not all testers want to learn the scripting languages of different automation tools. On the other hand automators aren't necessarily well aquainted with the application, so there are often communication problems.
- Testers can prepare test cases from the requirements and can therefore start even before the application has been developed. Automators must usually wait for at least a rudimentary GUI.
Resolving Patterns
Most recommended:
- DOMAIN-DRIVEN TESTING: Apply this pattern to get rid of this issue for sure. It helps you find the best architecture when the testers cannot also be automators
- OBJECT MAP: This pattern is useful even if you don't implement DOMAIN-DRIVEN TESTING because it forces the development of more readable scripts
Other useful patterns:
- KEYWORD-DRIVEN TESTING: This pattern is widely used already, so it will be not only easy to apply for your testers, but you will also find it easier to find automators able to implement it
- SHARE INFORMATION: If you have issues like Example 1. this is the pattern for you!
- TEST AUTOMATION FRAMEWORK: If you plan to implement DOMAIN-DRIVEN TESTING you will need this pattern too. Even if you don't, this pattern can make it easier for testers to use and help implement the automation
The NON-TECHNICAL-TESTERS Mind Map shows how the resolving patterns relate to other patterns.
.................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues
B2