Difference between revisions of "INADEQUATE COMMUNICATION"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................") |
m (Topic titles in capital letters) |
||
| 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-family: Arial; font-size: 16px">Issue Summary</span>= | + | =<span style="font-family: Arial; font-size: 16px">'''Issue Summary'''</span>= |
| − | + | <span style="font-family: Arial; font-size: 16px">This issue covers two frequently recurring problems:</span><br /> | |
| − | |||
* <span style="font-family: Arial; font-size: 16px">Testers don’t know what automation could deliver and the test automation team doesn’t know what testers need </span> | * <span style="font-family: Arial; font-size: 16px">Testers don’t know what automation could deliver and the test automation team doesn’t know what testers need </span> | ||
* <span style="font-size: 16px">Developers don't understand, don't know or don't care about the effect of their changes on the automation</span> | * <span style="font-size: 16px">Developers don't understand, don't know or don't care about the effect of their changes on the automation</span> | ||
| − | + | =<span style="font-family: Arial; font-size: 16px">'''Category'''</span>= | |
| − | =<span style="font-family: Arial; font-size: 16px">Category</span>= | + | <span style="font-family: Arial; font-size: 16px">Process</span> |
| − | + | =<span style="font-family: Arial; font-size: 16px">'''Examples'''</span>= | |
| − | =<span style="font-family: Arial; font-size: 16px">Examples</span>= | ||
| − | |||
| − | |||
# <span style="font-family: Arial; font-size: 16px">Test cases that should be automated are written very sparingly because "everybody knows what you have to do"... only automators do not</span> | # <span style="font-family: Arial; font-size: 16px">Test cases that should be automated are written very sparingly because "everybody knows what you have to do"... only automators do not</span> | ||
# <span style="font-family: Arial; font-size: 16px">Automators need help from some tester or specialist, but that person is not available or doesn't have time</span> | # <span style="font-family: Arial; font-size: 16px">Automators need help from some tester or specialist, but that person is not available or doesn't have time</span> | ||
| Line 16: | Line 12: | ||
# <span style="font-family: Arial; font-size: 16px">Testers, developers and automators work in different buildings, cities, time zones, or countries</span> | # <span style="font-family: Arial; font-size: 16px">Testers, developers and automators work in different buildings, cities, time zones, or countries</span> | ||
# <span style="font-family: Arial; font-size: 16px">Developers change the Software Under Test (SUT) without caring if it disrupts the automation or makes it harder</span> | # <span style="font-family: Arial; font-size: 16px">Developers change the Software Under Test (SUT) without caring if it disrupts the automation or makes it harder</span> | ||
| − | + | =<span style="font-family: Arial; font-size: 16px">'''Questions'''</span>= | |
| − | =<span style="font-family: Arial; font-size: 16px">Questions</span>= | + | <span style="font-family: Arial; font-size: 16px">Are testers and automators on the same team? If not, why not?</span><br /> <span style="font-family: Arial; font-size: 16px">Do developers notify automators when they want to use new components? Do automators report to development which components they cannot drive?</span><br /> <span style="font-family: Arial; font-size: 16px">How often do team members meet personally? How often in telephone conferences / live meetings?</span><br /> <span style="font-family: Arial; font-size: 16px">Do team members know each other? How about time or language differences?</span><br /> <span style="font-family: Arial; font-size: 16px">Do team members with the same role have the same experience / know-how? Do they speak the same "language"?</span> |
| − | + | =<span style="font-family: Arial; font-size: 16px">'''Resolving Patterns'''</span>= | |
| − | =<span style="font-family: Arial; font-size: 16px">Resolving Patterns</span>= | + | <span style="font-family: Arial; font-size: 16px">Most recommended:</span><br /> <span style="font-size: 16px">[[SHARE INFORMATION]]: this pattern is a no brainer for big and small automation efforts. Use it!</span><br /> <span style="font-size: 16px">[[WHOLE TEAM APPROACH]]: if your development team uses an agile process and you apply this pattern, you will not encounter this issue</span><br /> <br /> <span style="font-family: Arial; font-size: 16px">Other useful patterns:</span><br /> <span style="font-family: Arial; font-size: 16px">[[GET ON THE CLOUD]]: This pattern is especially useful if you are working with a distributed team</span><br /> <br /> <span style="font-size: 14px">................................................................................................................[[Main Page]] / Back to [[Process Issues]] / Back to [[Test Automation Issues]]</span></div> |
| − | |||
Latest revision as of 17:45, 30 April 2018
................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues
SHARE INFORMATION: this pattern is a no brainer for big and small automation efforts. Use it!
WHOLE TEAM APPROACH: if your development team uses an agile process and you apply this pattern, you will not encounter this issue
Other useful patterns:
GET ON THE CLOUD: This pattern is especially useful if you are working with a distributed team
................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues
Issue Summary
This issue covers two frequently recurring problems:
- Testers don’t know what automation could deliver and the test automation team doesn’t know what testers need
- Developers don't understand, don't know or don't care about the effect of their changes on the automation
Category
Process
Examples
- Test cases that should be automated are written very sparingly because "everybody knows what you have to do"... only automators do not
- Automators need help from some tester or specialist, but that person is not available or doesn't have time
- Testers do a lot of preparations to do manual testing that could be easily automated if only the automators knew about it
- Testers, developers and automators work in different buildings, cities, time zones, or countries
- Developers change the Software Under Test (SUT) without caring if it disrupts the automation or makes it harder
Questions
Are testers and automators on the same team? If not, why not?
Do developers notify automators when they want to use new components? Do automators report to development which components they cannot drive?
How often do team members meet personally? How often in telephone conferences / live meetings?
Do team members know each other? How about time or language differences?
Do team members with the same role have the same experience / know-how? Do they speak the same "language"?
Resolving Patterns
Most recommended:SHARE INFORMATION: this pattern is a no brainer for big and small automation efforts. Use it!
WHOLE TEAM APPROACH: if your development team uses an agile process and you apply this pattern, you will not encounter this issue
Other useful patterns:
GET ON THE CLOUD: This pattern is especially useful if you are working with a distributed team
................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues