quality-business-test

To validate implementation against PRD acceptance criteria with traceability, parse REQ and NFR documents to extract L1-L3 test scenarios, generate fixtures and mock contracts, and execute automated business tests that produce a traceability matrix.

You generate test fixtures and mock contracts from a PRD by using schema-derived, criteria-derived, and scenario-derived extraction to produce deterministic test data and mock service contracts for multi-layer business testing.

RFC 2119 priority mapping parses requirement keywords like MUST or SHOULD within PRD documents to classify extracted L1, L2, and L3 test scenarios by priority, ensuring automated tests focus on critical business rules first.

The best way to automate multi-layer business testing is using a generator-critic execution loop that progressively runs L1 interface, L2 business rule, and L3 scenario tests, automatically creating issues for any failures detected.

You need REQ-*.md and NFR documents to extract L1-L3 test scenarios, as the PRD-forward scenario extraction relies on parsing these specific markdown requirement formats to generate test cases and fixtures.

A generator-critic loop for automated business testing iteratively evaluates generated test scenarios and fixtures against PRD acceptance criteria, catching requirement regressions and policy gaps early during progressive layer execution.