Difference between revisions of "NON-TECHNICAL-TESTERS"
Jump to navigation
Jump to search
m (empty lines removed) |
|||
| Line 6: | Line 6: | ||
=<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 or API.</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">Most recommended:</span><br /> | ||
Revision as of 14:40, 25 June 2018
.................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues
.................................................................................................................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 or API.
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
.................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues
B2