test-planning

A test plan identifies required tests by analyzing code for coverage gaps and edge cases without writing test code. It maintains a record of findings to prioritize tests by observable risk and critical paths.

Yes, you can identify edge cases and coverage gaps for a specific branch or selected files. The analysis scopes to your chosen target to draft a focused test plan highlighting critical paths and major interaction points.

The best way to plan tests for public API boundaries is to analyze code insights to find coverage gaps. This generates a standalone plan prioritizing tests by observable risk and critical paths without implementing test code.

Yes, this test planning approach fits into a TDD workflow by providing test guidance without writing test code or refactoring plans. It drafts what tests to write based on code analysis, leaving implementation to you.

To prioritize tests by observable risk, generate a test plan that analyzes code for coverage gaps and edge cases. The plan maintains a record of findings to help you prioritize testing around critical paths and public API behavior.

A limitation of generating test plans from code analysis is that it does not write test code or provide refactoring plans. It only drafts what tests to write for public API behavior within a specific branch or selected files.