The test automation team is available full time and all the needed tools and machines are in place.
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.
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.
- 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.
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
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.