Guidelines to be followed for identification of Test Cases for Automation

1. Tests that need to run once and those that need frequent human intervention are usually not worth the investment to automate and have not been considered for automation.
2. As Automated testing can be used to verify the performance of application paths that are used with a high degree of frequency when the software is running in full production  
3. Mission critical processes like core activities are prime candidates for automated testing 
4. Repetitive Testing
5. Applications with Long Life span – Longer the application in production greater the benefits from automation.
6. Avoiding business scenarios where complex hardware is involved
7. Avoiding scenarios that require high degree of coding while automating so that script’s complexity is reduced and high maintainability of the script is ensured.
   

Approach for Automation Testing

Approach for automation testing involves building a strategy for automation testing starting from the requirement phase till to the deployment phase.
Test automation begins with the conditions, strategies and business rules given by the clients. Grouping of these similar conditions and business rules treated
as Test Case or Test Strategy.

Steps involved in Automation Testing
1.    Requirements gathering
2.    Understanding and Analyzing the requirements
3.    Grouping the requirements and business rules as Test Cases.
4.    Building the strategy for Automation
5.    Preparing the Design for Automation
6.    Preparing the Scripts for Automation
7.    Review of scripts
8.    Delivery to the client.

Design of the Approach for Test Automation