executing-qa

Execute adversarial QA by writing and running real tests against your feature branch to validate behavior and surface failures. When no test framework is detected, it produces a structured exploratory review instead.

When no test framework is detected, adversarial QA falls back to producing a structured exploratory review. This ensures behavior validation and failure surfacing continue without requiring external testing dependencies.

Yes, you need jq and git installed to execute feature branch QA. These dependencies support capability discovery, plan loading, and artifact rendering scripts that enforce structure and traceability throughout the validation process.

Capability discovery for feature branch testing works by probing the consumer's environment to select a test-framework path or exploratory review. This adapts the adversarial QA execution to available tools and renders a compliant results artifact.

A version-2 QA artifact is a structured results file containing capability reports, execution results, and requirement deltas. It enforces traceability and supports governance by providing an auditable record of adversarial QA validation.

Yes, you can use exploratory review instead of automated tests for feature branch validation. The system adapts to consumer capabilities, selecting exploratory review when no test framework is detected, and still renders a version-2 QA artifact for auditing.