What is the right time to start implementing QA automation?

• Long-term development and frequent releases
• Project’s all functionalities are stable and don’t need improvement
• A lot of routine work, which may lead for missing defects

The primary goal of automated testing is to save time, effort, and money on repetitive tests that don’t change frequently.

Automation could be expensive, if you don’t find out how and what to automated and you need consider the time (automation the test should not take much time compared to human)

Automation is recommended for

• Test cases that are executed repeatedly and requirements are not changing (ex: CRUDs)
• Large scale testing: testing across multiple platforms and configurations.
• Complex scenarios: test cases that involve multiple data inputs, many states calculations, and many interactions.
• Test cases which are time consuming
• High risk and business critical test cases
• Performance testing
• Approaches:
  • Data driven testing
  • Smoke testing
  • Regression testing

Automation is NOT recommended for

• One-time, ad-hoc or exploratory testing
• Testing a feature under development (Requirements changing freq.)
• Testing 3rd party service
• Cases where time and cost investment is too high
• Usability testing