qa-test-creation

To ensure test coverage before code review, validate acceptance criteria against existing tests and generate missing unit and end-to-end tests. This process checks every PRD item, creates meaningful assertions, and logs coverage gaps to inform pull request decisions.

Generate meaningful unit and E2E tests by evaluating feature requirements and creating assertions only when they provide valuable coverage. This avoids fake tests by targeting actual validation steps and ensuring every generated test covers a specific PRD acceptance criterion.

Automated coverage validation for PRD-driven features is the process of checking that every product requirement document item has corresponding unit and E2E tests. It identifies missing tests, generates necessary validation steps, and documents remaining gaps before code review.

Validate acceptance criteria by cross-referencing PRD items with existing tests, generating missing unit and E2E tests, and logging observations. Documenting test gaps provides clear notes for PR decisions and closes validation tasks with transparent QA records.

Automate test generation when a feature branch lacks sufficient unit or E2E tests for its acceptance criteria. Generation should occur during validation before code review, ensuring new tests provide meaningful coverage rather than trivial or fake assertions.