terraform-testing
Testing Terraform configurations with native tests, Terratest, and validation frameworks
Discover tools testing skills, compare source repositories and read the instructions for each workflow.
Testing Terraform configurations with native tests, Terratest, and validation frameworks
Write production-grade React tests with Testing Library, MSW, and comprehensive coverage patterns
Test Node.js applications with Jest including unit tests, integration tests, mocking, code coverage, and CI/CD integration
JavaScript testing with Jest, Vitest, and Testing Library for comprehensive test coverage.
Backend testing strategies and test automation. Unit, integration, E2E, and load testing with best practices.
Use when about to claim work is complete, fixed, or passing. Run verification commands and confirm output before making any success claims. Evidence before assertions.
Use when implementing any feature or bugfix. Write the test first, watch it fail, write minimal code to pass. Red-Green-Refactor cycle.
Use when encountering any bug, test failure, or unexpected behavior. Always find root cause before attempting fixes. Evidence before assertions.
Produce a test checklist from a feature description, bug report, or spec. Use when the user asks for test plan/测试清单/测试用例建议.
Testing patterns, pyramid, TDD
Use when (1) verifying a feature is complete against acceptance criteria, (2) running QA checklist before release, (3) validating PR changes meet requirements. Performs systematic QA verification with documente...
Write tests that start with acceptance criteria, then add implementation tests for robustness. Use when writing unit tests (Vitest), end-to-end tests (Playwright), visual regression tests, or accessibility test...
Configure test infrastructure with fixtures, helpers, and enhanced coverage. Use when setting up comprehensive testing. Triggers on "setup testing", "test infrastructure", "test helpers", "test fixtures".
Write tests for Zod schemas. Use when testing entity schemas, DTO validation, query parameter schemas, or any schema validation rules. Triggers on "test schema", "schema tests", "test validation", "test zod".
Write tests for MockDB (in-memory) repository implementations. Use when testing MockDB repositories, in-memory data access, or mock repository behavior. Triggers on "test mockdb", "mockdb tests", "test mock rep...
Guide for testing repository layer. Use when asked to test repositories or data access layer. Directs to implementation-specific testing skills.
Test resource services that handle CRUD operations. Use when testing services that extend BaseService with authorization and event emission. Triggers on "test note service", "test resource service", "test crud...
Write tests for MongoDB repository implementations. Use when testing MongoDB repositories, setting up MongoDB test infrastructure, or testing database operations. Triggers on "test mongodb", "mongodb tests", "t...
Test utility services that handle external APIs or authorization logic. Use when testing services like AuthenticationService or AuthorizationService. Triggers on "test auth service", "test utility service", "te...
Test controllers that handle HTTP requests. Use when testing controller methods that call services and return responses. Triggers on "test controller", "test note controller".
Test middleware functions. Use when testing authentication, validation, or other middleware. Triggers on "test middleware", "test auth middleware", "test validation middleware".
Test route configurations with integration-style tests. Use when testing complete request/response cycles through routes. Triggers on "test routes", "test note routes", "integration test".
Guide for testing service layer. Use when asked to test services. Directs to implementation-specific testing skills.
Test the SSE events router and real-time event streaming. Use when testing Server-Sent Events endpoint or event authorization. Triggers on "test events", "test sse", "test events router", "test real-time".
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.