automation-candidate-criteria

Identify automation candidates by applying decision tree criteria to functional guarantees like domain rules, state transitions, business events, API contracts, and async workflows to yield a clear yes/no decision with rationale.

You should not automate infrastructure setup, environment verification, database migrations, or pure deployment checks. Filtering these out prevents wasting resources on non-functional boundaries that should remain manual or infrastructure-focused.

You need a decision tree for test automation criteria when your test plans contain mixed functional guarantees and infrastructure setup tasks, requiring ruthless filtering to extract valuable cross-service interactions for automation.

Apply the automation candidate criteria to your sample test plan to evaluate domain rules and business events. This process returns a clear yes/no decision for each test case with an actionable rationale.

Yes, the automation criteria framework explicitly supports async workflows and API contracts. It scopes cross-service interactions and state transitions to determine exactly what functional guarantees qualify for automation.