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.