assess-testing

To define a testing strategy, you assess the project to recommend frameworks, establish testing pyramid distribution, and set coverage targets. This approach evaluates tools like Vitest or Jest and records the decision as an ADR for future reference.

Choosing a testing framework during a refactor involves evaluating your project guidelines and existing adoption files. The assessment uses a resolution cascade of argument, existing adoption, or full evaluation to recommend the most consistent testing approach.

Testing coverage target selection integrates with your tech stack by updating the project's `tech-stack.md` file. This ensures the chosen testing strategy, including frameworks and coverage goals, aligns with and is documented within your current technology adoption.

Yes, you can use this testing strategy assessment with existing adoption files. The process follows a resolution cascade that prioritizes existing adoption records before performing a full assessment based on your project guidelines.

You should document testing decisions as an Architecture Decision Record (ADR) when finalizing your testing strategy. Recording the framework selection and coverage targets as an ADL or ADR ensures code quality decisions are logged for future reference and team alignment.