test-suggest

To generate unit test cases for source modules, this skill analyzes implementation logic and existing test conventions to produce prioritized, actionable test specifications. It ranks suggestions into Must-have, Should-have, and Nice-to-have categories based on identified failure modes.

Risk-based prioritization for unit testing ranks proposed test cases into Must-have, Should-have, and Nice-to-have categories. This approach targets high-leverage coverage gaps by focusing on failure modes, boundary conditions, and side effects rather than just hitting coverage metrics.

You can use test-driven development with existing test conventions because the skill inspects your codebase to match your current test frameworks, assertion styles, and naming conventions. This context-aware design ensures generated test cases integrate seamlessly with your established testing workflow.

To identify missing edge cases for error handling and boundary inputs, the skill analyzes your source code to propose specific, high-leverage test cases. It targets failure modes and boundary conditions to catch real bugs before you write a single line of test code.

This testing approach works for integration and contract testing scenarios, as well as unit testing. It generates prioritized test case specifications by analyzing implementation logic, satisfying requirements for framework-specific assertion styles and failure mode identification across these testing levels.

You should not use automated test case suggestions when you only need to increase raw code coverage metrics without targeting actual failure modes. The tool is designed to solve the blank page problem by proposing high-leverage tests that catch real bugs rather than superficially hitting coverage targets.