feature-test_skill

Overview

This skill helps create and verify tests for newly implemented features. It guides writing unit and integration tests, covering edge cases, and building reusable fixtures to ensure deterministic, maintainable test suites.

How this skill works

The skill inspects the new feature surface and produces a checklist-driven test plan that maps public methods, endpoints, and interactions to test cases. It recommends test doubles, fixtures, and environment choices, then reports implementation status using a simple Complete/Partial/Blocked/Skipped rubric. It focuses on single-behavior tests, realistic test data, and isolation to minimize flakiness.

When to use it

• After implementing new functions, classes, or API endpoints
• When adding integration points between components or services
• While preparing for release to ensure edge cases are covered
• When creating or refactoring test fixtures and shared factories
• If tests are flaky or nondeterministic and need stabilization

Best practices

• Write one assertion intent per test and name tests to reflect expected behavior
• Mock external dependencies; use in-memory stores or test doubles for integration work
• Cover boundary values, null/undefined inputs, and error paths explicitly
• Create reusable fixtures and factories; ensure setup/teardown removes shared state
• Prefer deterministic timing and avoid sleeping; simulate timeouts and retries where possible

Example use cases

• Unit tests for all public methods in a new library module with mocks for IO
• Integration tests validating API request/response contracts and database changes
• Edge-case tests for concurrency, race conditions, and large input bounds
• Reusable fixtures for user records to speed up test creation across suites
• Test plan report that marks each checklist item as Complete, Partial, Blocked, or Skipped