Design and review test suites using test pyramid principles.
npx skills add https://github.com/I2olanD/dotfiles --skill test-design-i2oland
Please help me install this Agent Skill. Skill: test-design Source: https://github.com/I2olanD/dotfiles/tree/main/.config/opencode/skill/test-design Command: npx skills add https://github.com/I2olanD/dotfiles --skill test-design-i2oland
This Skill provides a pragmatic blueprint for test design based on the pyramid model, helping teams structure, review, and evolve their test suites.
Use the guide to audit or design a test suite. Identify your project's testing framework, categorize tests into unit, integration, and E2E, and apply the recommended distributions, naming conventions, and review practices to improve feedback speed and confidence.
High-intent search queries and answers about installing and using this skill.
The recommended test distribution follows the test pyramid model: 60-70% unit tests, 20-30% integration tests, and 5-10% E2E tests. This distribution enables fast feedback and reliable software delivery by keeping slow, brittle E2E tests to a minimum.
To structure test suites using AAA patterns, apply framework-agnostic conventions for test naming, file organization, and the Arrange-Act-Assert structure. This approach works across Jest, Pytest, and other common frameworks to maintain consistent test design.
Yes, this test design approach works with Jest, Pytest, and other common testing frameworks. It provides framework-agnostic conventions for naming, file organization, and coverage targets, ensuring broad applicability across different technology stacks.
To audit an existing test suite, categorize your tests into unit, integration, and E2E layers. Compare the current distribution against pyramid targets, review AAA structure adherence, and identify anti-patterns to improve coverage quality and feedback speed.
Your test suite should follow test pyramid principles to enable fast feedback and reliable software delivery. By enforcing a pyramid-based distribution, you minimize slow E2E tests and maximize quick unit tests, reducing execution time and maintenance costs.
A strict test pyramid distribution may not suit all projects, as complex integration-heavy architectures might require more mid-level tests. The 60-70% unit and 5-10% E2E targets are guidelines, meaning teams should adjust distributions based on specific application needs.
latestaiagentsGenerate unit, integration, and API tests for Vitest, Jest, and pytest.
JeffallanDevelop scalable Salesforce applications with Apex, LWC, SOQL, and Salesforce DX.
akarazhevEnforce Java 25 code style conventions across Java modules.
wodsmithRoute testing questions to unit, integration, or E2E test types.
