detect-test-harness

Test harness detection inspects scan-index manifests, CI workflow files, and configuration to infer the real test framework and invocation details. It pattern-matches repository signals against an embedded harness catalog to produce a precise TEST_HARNESS record.

Deterministic test generation verification applies during pre-flight phases by detecting runnable test harness configurations to enable baseline-green checks. It requires parsing JSON scan-index input and resolving primary runner priority for subsequent runner execution planning.

To generate test-harness.yaml, provide scan_index_path, codebase_root, and output_path. The skill parses JSON scan-index input, matches against a canonical harness catalog, resolves primary runner priority, and produces the structured test-harness.yaml artifact at the output path.

Framework detection performs a light runnability check without executing tests. It records when dependency installation is required or returns a no-harness-detectable status when nothing runnable can be identified across unit and E2E tiers.

When no test harness is detectable, the process fails with a no-harness-detectable status. This occurs after parsing JSON scan-index input and matching repository signals against the canonical harness catalog without identifying any runnable test framework.