You have a list of cases for automation. Which candidates are the top priority for automation, which are less suitable, and which are not suitable at all? How would you prioritize?

Prioritization of automation cases depends on several factors:

• Candidates for automation first:

  • Repetitive and frequently executed tests (regression, smoke).
  • Tests with clear, stable verification criteria.
  • Tests requiring large amounts of data or complex scenarios that are difficult to perform manually.
  • Critical business functionalities.

• Less suitable:

  • Tests with frequent requirement or interface changes.
  • Tests heavily dependent on visual perception (UI without stable identifiers).
  • Scenarios requiring complex environment setup that is difficult to automate.

• Not suitable for automation:

  • Exploratory testing.
  • Tests requiring subjective assessment (usability, UX).
  • One-time or rarely performed checks.

Prioritization is usually based on:

1. Test execution frequency.
2. Importance of the functionality.
3. Stability of the tested functionality.
4. Resources and time for automation.

This approach maximizes the return on automation and reduces testing support costs.