writing-skills
TDD for process documentation - test with subagents before writing, iterate until bulletproof
TDD for process documentation - test with subagents before writing, iterate until bulletproof
Test Node.js applications with Jest including unit tests, integration tests, mocking, code coverage, and CI/CD integration
This skill should be used when the user asks to "write tests first", "use TDD", "test-driven development", "red green refactor", "test first", "add unit tests before code", "write regression test first", "safe refactor with tests", or when TDD mode is active and the user makes any coding request that affects behavior (features, bugs, refactors).
Pick and run the smallest correct validation step (checks → focused Jest by path → broader suites). Use whenever you modify code and need confidence quickly.
Testing patterns and requirements for Claude Family projects
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", "test mongo repository", "mongodb test setup".
Claude writes reliable E2E tests using Playwright for browser automation. Use when writing end-to-end tests, implementing Page Object Model, visual regression testing, API mocking, or cross-browser testing.
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".
Validate quality and security through comprehensive testing. Functional testing, integration/system testing, performance testing, security testing, compliance validation, user acceptance testing (UAT), and defect management.
Provides Go standard testing package expertise and best practices. Ensures proper table-driven test patterns, subtests organization, benchmark implementation, and test coverage strategies. Specializes in testing.T/testing.B usage, test helpers, mock interfaces, race detection, and integration testing patterns following Go conventions. Use when: writing Go test files (_test.go), implementing table-driven tests with subtests (t.Run), creating benchmark tests (testing.B), writing example tests for documentation, implementing test helpers and fixtures, mocking interfaces for unit tests, measuring code coverage with go test -cover, detecting race conditions with -race flag, or organizing integration tests in Go projects.
ユーザーストーリーからE2Eテストを作成・更新するスキル。ストーリーに基づいてPlaywrightテストを生成する。
Guide experienced developers through TDD failure scenarios and recovery procedures when tests behave unexpectedly
Use when a project needs a verification plan for acceptance testing in real-world scenarios
Use to trace requirements through implementation. Maps acceptance criteria to code and tests.
This skill provides patterns and best practices for generating and organizing tests. It covers unit testing, integration testing, test data factories, and coverage strategies across multiple languages and frameworks.
Use after implementation complete to verify all tasks done, update roadmap, run full test suite, and create final report - ensures implementation completeness before finishing development branch
E2E testing for Umbraco backoffice extensions using Playwright and @umbraco/playwright-testhelpers
Testing patterns including unit, integration, E2E tests and language-specific frameworks.