test-plan

To create a structured test plan without writing test code, you analyze the target code to extract signatures and return values, decompose the input space into canonical, boundary, and invalid categories, and map out test architecture and mock boundaries.

You need to decompose the input space before writing tests when planning comprehensive coverage for complex modules, ensuring you capture canonical, empty, boundary, invalid, and adversarial input categories to prioritize test cases effectively.

To identify which external systems to mock for a module test architecture, you extract code contracts and side effects using file reading and pattern matching tools, then recommend mock boundaries based on the extracted dependencies.

Yes, you can generate a test plan for a specific module like order.js without coding by instructing the tool to analyze the target function, extract its contracts, and output a structured test plan table ready for developers.

The best way to define input categories for unit and integration testing is to analyze target code contracts and decompose the input space into canonical, empty, boundary, invalid, and adversarial categories with prioritized test cases.

Generating a test plan without writing test code is limited to analysis, contract extraction, and planning; it outputs a structured table and architecture recommendations but does not execute tests or generate the actual test code itself.