Saturday, July 17, 2010

Automation Strategy

Test automation strategy forms the most important stage in any project. It is always important to draw boundaries before hand since the scripting to provide solution can be endless. Some of the important points to consider in a strategy is:

1. Define beginning of testing of application.
2. Limit test data so that scripting complexity is reduced.
3. Handling of errors and different conditions
4. Last and most important - number of test cases to be automated.

These are some basic points to consider defining strategy no matter how experienced or how new you are as an automation engineer.

Next the automation details:
1. Automation approach
2. Automation deliverables
3. Estimation for analyzing, framework design, scripting, unit testing, integration testing and final suite delivery. Estimated maintenance effort for a regular period of time will be an added advantage to mention.

The remaining points to consider in strategy are in the interest of general testing which usually the test leads/ analysts will be interested in.
1. Prerequisites
2. Assumptions
3. Risks
4. Time line details
5. Environmental requirements/ details
6. Issues and other logs


The last portion of the strategy could be about the return on investment - which is a complex and subjective calculation. Every company/ project can calculate these on various methods and scales depending on how it is implemented and used.

No comments: