Enforce Given-When-Then structure and parameterized patterns in test code.
npx skills add https://github.com/tttol/dotfiles --skill test-code-tttol
Please help me install this Agent Skill. Skill: test code Source: https://github.com/tttol/dotfiles/tree/main/config/skills/test-code Command: npx skills add https://github.com/tttol/dotfiles --skill test-code-tttol
Writing tests can be inconsistent across teams and languages, leading to unreadable tests, flaky runs, and higher maintenance costs. This guideline provides a structured approach to writing clear, maintainable tests that stay reliable as projects evolve.
Begin by reading this guideline and apply the Given-When-Then pattern to your existing tests.
High-intent search queries and answers about installing and using this skill.
The Given-When-Then structure organizes unit tests into setup, action, and verification phases. This pattern improves test readability and maintainability by clearly separating the initial state, the action being tested, and the expected outcome assertions.
Parameterized tests cover multiple inputs with minimal duplication by feeding various data sets into a single test method. This approach ensures consistent testing across different scenarios while avoiding the maintenance cost of writing separate, repetitive unit tests for each case.
Yes, these test code guidelines are cross-language applicable. Developers can apply the same best practices for unit, integration, and end-to-end tests across projects and CI pipelines in any programming language to ensure consistent test code quality.
Avoiding inline logic in test code prevents flaky runs by ensuring tests focus strictly on assertions rather than complex calculations. Keeping tests free of inline logic maintains readability, reduces maintenance costs, and ensures tests stay reliable as projects evolve.
This approach works for unit, integration, and end-to-end tests. The guidelines enforce explicit Given-When-Then structures and clear assertions across all testing levels, ensuring readable, maintainable tests that stay reliable throughout your CI pipelines.
Dmccarty30Create isolated Git worktrees with dependency installation and baseline tests.
petrkohutGenerate end-to-end automated tests for existing software features.
bswrundquistAnalyze code test coverage to identify and prioritize high-risk untested code.
knckknckStandardize Go code quality and style across projects.
