Management Patterns

Management patterns show how to manage test automation both as an autonomous project or integrated in the development process. The table below gives a list of the Management patterns with a short description. The Management Patterns Mind Map shows which other patterns are used by the project patterns.

Pattern	Description
AUTOMATE EARLY	Start to automate as early as possible. The sooner automated tests can be run the sooner you can see results
AUTOMATION ROLES	Test automation team needs many different skills, and people to take different roles.
DEDICATED RESOURCES	The test automation team is available full time and all the needed tools and machines are in place.
DEPUTY	Appoint a deputy to all important knowledge carriers
DO A PILOT	Start a pilot project to explore how to best automate tests on the application.
GET ON THE CLOUD	Instead of using local machines put the project on one or more virtual machines
GET TRAINING	Plan to get training for all those involved in the test automation project.
KNOW WHEN TO STOP	Not all test cases can or should be automated.
MANAGEMENT SUPPORT	Earn management support. Managers should only support sound and well-reasoned activities, so we need to work at selling the idea initially and then keep them up-to-date with progress and issues.
MIX APPROACHES	Don’t be afraid to use different tools or approaches
PLAN SUPPORT ACTIVITIES	Plan time and resources not only for the project goals, but also for support activities
PREFER FAMILIAR SOLUTIONS	Given the same benefits prefer a tool or a scripting language that is already known in-house.
RIGHT TOOLS	Select the right tools for your application, environment, people, budget and level of testing
SELL THE BENEFITS	Inform management before and during test automation about achievable and achieved benefits.
SET CLEAR GOALS	Define the project objectives from the very beginning.
SSIDE-BY-SIDE	Determine which automation tool is best for you by trying them side by side
TESTABLE SOFTWARE	Locate what kind of implementations in the Software Under Test (SUT) may make test automation difficult or impossible and find a solution as early as possible.
TEST AUTOMATION BUSINESS CASE	Present a business case as for any other project, but provide also factors typical for test automation
TEST AUTOMATION OWNER	Appoint an owner for the test automation effort

Main Page
Back to Test Automation Patterns
Back to Process Patterns
Forward to Design Patterns