generate-tests

Generate test cases by analyzing function inputs, outputs, and side effects to identify normal, edge, and error scenarios. Write assertions for each case with clear expected values, structured naming conventions, and setup/teardown scaffolding to ensure complete code coverage.

Edge cases include empty inputs, boundary conditions, null values, and error states. Comprehensive test generation identifies these scenarios automatically, helping you validate that your code handles not just happy paths but also corner cases that commonly cause bugs.

In TDD, generate test cases before writing implementation code. This skill identifies functional and technical requirements, produces structured test assertions, and provides coverage reporting aligned with established references to ensure refactors don't break existing functionality.

Yes. Comprehensive test cases catch regressions when refactoring by validating that function behavior, outputs, and side effects remain unchanged. Generated assertions provide clear coverage reporting to confirm refactored code still satisfies all original requirements.

Use clear naming conventions tied to test scenarios, implement descriptive setup and teardown scaffolding, and write assertions with explicit expected outputs for each case. This produces maintainable tests that document expected behavior and simplify debugging when failures occur.

No. Test generation analyzes function behavior to automatically identify normal, edge, and error cases, removing the manual burden of scenario discovery. This ensures consistent coverage across codebases and reduces the risk of incomplete test suites.