Difference between revisions of "DEDICATED RESOURCES"
m (Topic titles in capital letters) |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
<span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Patterns]] / Back to [[Test Automation Patterns]]</span><br /> | <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Patterns]] / Back to [[Test Automation Patterns]]</span><br /> | ||
=<span style="font-size: 16px">'''Pattern summary'''</span>= | =<span style="font-size: 16px">'''Pattern summary'''</span>= | ||
| − | <span style="font-size: 16px">The test automation team is available full time and all the needed tools and machines are in place.</span | + | <span style="font-size: 16px">The test automation team is available full time and all the needed tools and machines are in place.</span> |
=<span style="font-size: 16px">'''Category'''</span>= | =<span style="font-size: 16px">'''Category'''</span>= | ||
<span style="font-size: 16px">Management</span> | <span style="font-size: 16px">Management</span> | ||
=<span style="font-size: 16px">'''Context'''</span>= | =<span style="font-size: 16px">'''Context'''</span>= | ||
| − | <span style="font-size: 16px">This pattern is applicable if you have a tight schedule for your test automation project, or if you want to build a significant test automation regime that will be used by many testers.</span><br /> <span style="font-size: 16px">This pattern is not applicable for very small organisations where, for example, there are only one or two testers, and they are doing automation work in parallel with testing activities.</span | + | <span style="font-size: 16px">This pattern is applicable if you have a tight schedule for your test automation project, or if you want to build a significant test automation regime that will be used by many testers.</span><br /> <span style="font-size: 16px">This pattern is not applicable for very small organisations where, for example, there are only one or two testers, and they are doing automation work in parallel with testing activities.</span> |
=<span style="font-size: 16px">'''Description'''</span>= | =<span style="font-size: 16px">'''Description'''</span>= | ||
<span style="font-size: 16px">A test automation team is assigned to work on test automation full-time, without other responsibilities. Any, tools, utilities, machines or other resources are provided as needed. You can get the help of specialists when you need it.</span> | <span style="font-size: 16px">A test automation team is assigned to work on test automation full-time, without other responsibilities. Any, tools, utilities, machines or other resources are provided as needed. You can get the help of specialists when you need it.</span> | ||
| Line 22: | Line 22: | ||
<span style="font-size: 16px">''[[AD-HOC AUTOMATION]]''</span><br /> <span style="font-size: 16px">''[[FALSE FAIL]]''</span><br /> ''<span style="font-size: 16px">[[FLAKY TESTS]]</span>''<br /> ''<span style="font-size: 16px">[[INADEQUATE TECHNICAL RESOURCES]]</span>''<br /> <span style="font-size: 16px">''[[INCONSISTENT DATA]]''</span><br /> <span style="font-size: 16px">''[[NO PREVIOUS TEST AUTOMATION]]''</span><br /> <span style="font-size: 16px">''[[SCHEDULE SLIP]]''</span><br /> ''<span style="font-size: 16px">[[HARD-TO-AUTOMATE RESULTS]]</span>'' | <span style="font-size: 16px">''[[AD-HOC AUTOMATION]]''</span><br /> <span style="font-size: 16px">''[[FALSE FAIL]]''</span><br /> ''<span style="font-size: 16px">[[FLAKY TESTS]]</span>''<br /> ''<span style="font-size: 16px">[[INADEQUATE TECHNICAL RESOURCES]]</span>''<br /> <span style="font-size: 16px">''[[INCONSISTENT DATA]]''</span><br /> <span style="font-size: 16px">''[[NO PREVIOUS TEST AUTOMATION]]''</span><br /> <span style="font-size: 16px">''[[SCHEDULE SLIP]]''</span><br /> ''<span style="font-size: 16px">[[HARD-TO-AUTOMATE RESULTS]]</span>'' | ||
=<span style="font-size: 16px">'''Experiences'''</span>= | =<span style="font-size: 16px">'''Experiences'''</span>= | ||
| − | <span style="font-size: 16px">If you have used this pattern, please | + | |
| + | <span style="font-size: 16px">If you have used this pattern and would like to contribute your experience to the wiki, please go to [[Feedback]] to submit your experience or comment.</span><br /> <br /> | ||
| + | |||
| + | <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Patterns]] / Back to [[Test Automation Patterns]]</span></div> | ||
Latest revision as of 14:45, 21 August 2018
.................................................................................................................Main Page / Back to Management Patterns / Back to Test Automation Patterns
Pattern summary
The test automation team is available full time and all the needed tools and machines are in place.
Category
Management
Context
This pattern is applicable if you have a tight schedule for your test automation project, or if you want to build a significant test automation regime that will be used by many testers.
This pattern is not applicable for very small organisations where, for example, there are only one or two testers, and they are doing automation work in parallel with testing activities.
Description
A test automation team is assigned to work on test automation full-time, without other responsibilities. Any, tools, utilities, machines or other resources are provided as needed. You can get the help of specialists when you need it.
Implementation
Some suggestions:
- A test automation project requires possibly more effort than a software development project and should be done as a FULL TIME JOB.
- PLAN SUPPORT ACTIVITIES so that you can get hold of specialists (for instance data base managers) when you need them.
- Tools and machines to run the tests need to be available, and ideally dedicated to running automated tests. GET ON THE CLOUD for cost-efficiency.
- SHARE INFORMATION: tell management that you will not be able to finish the project successfully if the team cannot concentrate completely on it. If this is not possible for the duration of the project, then at least at the beginning of the project.
If you have FLAKY TESTS you should check if the cause could be that your resources (machines, databases, network) are used concurrently by some other application. If this is the case, see to it that you get the resources you need when you need them for your exclusive use.
Potential problems
It is often the case that resources are severely limited, but expecting people to "do test automation in their spare time" is very unlikely to work, and is not efficient.
Issues addressed by this pattern
AD-HOC AUTOMATION
FALSE FAIL
FLAKY TESTS
INADEQUATE TECHNICAL RESOURCES
INCONSISTENT DATA
NO PREVIOUS TEST AUTOMATION
SCHEDULE SLIP
HARD-TO-AUTOMATE RESULTS
Experiences
If you have used this pattern and would like to contribute your experience to the wiki, please go to Feedback to submit your experience or comment.