unit-testing

wmeints's avatarfrom wmeints

Use this skill to write or modify unit-tests in the application for non-component files.

⭐2stars🔀0forks📁View on GitHub🕐Updated Jan 3, 2026

When & Why to Use This Skill

This Claude skill automates the creation and modification of unit tests for non-component files, significantly enhancing code reliability and development speed. By leveraging project-specific workflows, it ensures that backend logic and utility functions are thoroughly validated, helping developers maintain high code coverage and prevent regressions in complex software environments.

Use Cases

  • Backend Logic Validation: Automatically generate unit tests for complex business logic and utility functions to ensure functional correctness before deployment.
  • Test Suite Maintenance: Efficiently update or refactor existing unit tests when underlying non-component code changes, reducing manual effort and technical debt.
  • Project-Specific Testing: Execute specialized testing workflows tailored for different architectural layers, such as 'portal' or 'api' projects, ensuring compliance with internal standards.
  • Edge Case Detection: Identify and create test cases for boundary conditions and edge cases in non-UI code that might be missed during manual test authoring.
nameunit-testing
descriptionUse this skill to write or modify unit-tests in the application for non-component files.

Unit-testing

Use this skill to write or modify unit-tests in the application for non-component files. You should not use this skill when creating tests for components!

Testing workflows

  • Use the workflow located in ./workflows/portal-testing.md for unit-testing in the portal project.
  • Use the workflow located in ./workflows/api-testing.md for unit-testing in the api project.