[Me] :- Guruji, what is the most common methodology to adopt while looking for an automation project.
[Guruji]:- There is quite a standard methodology if adopted will make your life easier while looking at automation for any project. For the sake of your understanding, I have listed the tasks and deliverables from the work packets
| Tasks | Description | Deliverables |
| Identification of Automation Objectives/Test Requirements Study | Ø Understanding the objectives of Automation for design of an effective test architecture | Test Automation Strategy Document |
| Ø Understanding of the test requirements/application requirements for automation | ||
| Identification of Tool | Ø Normally done in the proposal stage itself | None |
| Ø Application of Tool Selection Process of eTest Center to arrive at the best fit for the given automation objectives | ||
| Script Planning & Design | Ø Design of Test Architecture | Design Document |
| Ø Identification of Reusable functions | ||
| Ø Identification of required libraries | ||
| Ø Identification of test initialization parameters | ||
| Ø Identification of all the scripts | ||
| Ø Preparation of Test design document – Application of Naming Conventions | ||
| Ø Test Data Planning | ||
| Test Environment Setup | Ø Hardware | None |
| Ø Software – Application, Browsers | ||
| Ø Test Repositories | ||
| Ø Version Control Repositories | ||
| Ø Tool setup | ||
| Development of Libraries | Ø Development of libraries | Phased delivery if applicable |
| Ø Debug/Testing of libraries | ||
| Development of Scripts | Ø Development of scripts | Phased delivery if applicable |
| Ø Debug/Testing of scripts | ||
| Development of Test Suites | Ø Integration of Scripts into test Suites | Test Suites & Libraries |
| Ø Debug/Testing of Suites | ||
| Deployment/Testing of Scripts | Ø Deployment of Test Suites | Test Run Results, Defect Reports, Test Report |