Testing Test Writing
Your approach to handling testing test writing. Use this skill when working on files where testing test writing comes into play.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install leaderiop-hex-di-testing-test-writing
Repository
Skill path: .claude/skills/testing-test-writing
Your approach to handling testing test writing. Use this skill when working on files where testing test writing comes into play.
Open repositoryBest for
Primary workflow: Write Technical Docs.
Technical facets: Full Stack, Tech Writer, Testing.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: leaderiop.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install Testing Test Writing into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/leaderiop/hex-di before adding Testing Test Writing to shared team environments
- Use Testing Test Writing for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: Testing Test Writing description: Your approach to handling testing test writing. Use this skill when working on files where testing test writing comes into play. --- # Testing Test Writing This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle testing test writing. ## Instructions For details, refer to the information provided in this file: [testing test writing](../../../agent-os/standards/testing/test-writing.md) --- ## Referenced Files > The following files are referenced in this skill and included for context. ### ../../../agent-os/standards/testing/test-writing.md ```markdown ## Test coverage best practices - **Write Minimal Tests During Development**: Do NOT write tests for every change or intermediate step. Focus on completing the feature implementation first, then add strategic tests only at logical completion points - **Test Only Core User Flows**: Write tests exclusively for critical paths and primary user workflows. Skip writing tests for non-critical utilities and secondary workflows until if/when you're instructed to do so. - **Defer Edge Case Testing**: Do NOT test edge cases, error states, or validation logic unless they are business-critical. These can be addressed in dedicated testing phases, not during feature development. - **Test Behavior, Not Implementation**: Focus tests on what the code does, not how it does it, to reduce brittleness - **Clear Test Names**: Use descriptive names that explain what's being tested and the expected outcome - **Mock External Dependencies**: Isolate units by mocking databases, APIs, file systems, and other external services - **Fast Execution**: Keep unit tests fast (milliseconds) so developers run them frequently during development ```