bmad-tea

Assessing testing risk involves evaluating architecture, test data, observability, and security concerns to produce a defensible go/no-go recommendation. This Skill analyzes readiness by mapping requirements to tests and prioritizing coverage based on business impact and failure probability.

Risk-based test architecture prioritizes coverage by impact and failure risk to recommend scalable testing patterns. It guides the balance between API and E2E testing by evaluating framework choices, fixtures, and test levels to ensure comprehensive quality gate integration.

Mapping non-functional requirements to tests involves evaluating NFR readiness across scalability, security, and deployability concerns. This process identifies testability gaps in the architecture by analyzing structural evaluation criteria and tracing requirements to existing test artifacts.

Yes, this testing risk assessment applies to API, UI, and backend service projects. It evaluates backend service quality readiness by analyzing architecture, test data, and observability concerns to determine appropriate CI/CD governance and test automation strategy.

Evaluating CI/CD quality gates requires analyzing deployability concerns, test architecture, and automation strategy within your pipeline. This Skill provides structured evaluation of these elements to determine when a quality gate should pass or fail during release preparation.

You need to provide relevant requirements, architecture notes, or existing test artifacts. The Skill uses these inputs to analyze testing risk, assess coverage gaps, choose appropriate test levels, and produce a go/no-go recommendation for your software system.