marsai:dev-unit-testing

Unit testing validation in this workflow is handled by Gate 3, which dispatches a QA Analyst to write tests and verify that implemented code meets acceptance criteria. It filters implementation files through a testable-layer allow-list and applies test-driven development practices.

Generating a coverage report and traceability matrix requires dispatching a QA Analyst to run tests and produce structured outputs. The process verifies code against acceptance criteria and generates a handoff to the next gate if coverage meets the 85% threshold.

No, you cannot start Gate 3 unit testing without providing implementation files. You must also supply a unit ID and acceptance criteria to initiate the process, which filters your files through a testable-layer allow-list before generating tests.

When unit test coverage falls below the required 85% threshold, the automation triggers an escalation. It supports iterative testing by automating re-tests to help you meet the strict test-driven development validation requirements.

Completing Gate 3 unit tests generates structured outputs including a Testing Summary, Coverage Report, Traceability Matrix, and Handoff to Next Gate. These documents ensure code quality and track acceptance criteria verification.