skills.rest
eymass
eymassCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tests-implementation

Define contract, failure flow, invariant, integration, and regression tests.

1|1|Updated Mar 6, 2026
Search Tags:#testing#code-quality#unit-testing#integration-testing#tests#test-automation#test-strategy
One-click install
npx skills add https://github.com/eymass/swe-plugin --skill tests-implementation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tests-implementation
Source: https://github.com/eymass/swe-plugin/tree/main/skills/tests-implementation
Command: npx skills add https://github.com/eymass/swe-plugin --skill tests-implementation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide provides a structured approach to testing that ensures software reliably keeps its promises by focusing on critical failure modes, invariants, and end-to-end workflows while avoiding test-coverage chasing.

Core Features & Use Cases

  • Mindset-driven testing philosophy: push back on naive tests and focus on contracts, failure flows, invariants, and integration quality.
  • Structured test types: contract tests, failure flow tests, invariant tests, integration tests, and regression tests, plus data seeding and project-structure guidelines.
  • Practical workflow: seeds data directly into the database, seeds helpers, and a recommended project layout to organize tests by domain.

Quick Start

Begin by clarifying the code's promises, identify failure modes, and draft contract, failure, invariant, integration, and regression tests before writing any test.

Frequently Asked Questions about tests-implementation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to structure unit and integration tests for robust code?▼

The best way to structure unit and integration tests is to organize them by domain and focus on verifying contracts, failure flows, and invariants rather than simply chasing test coverage metrics.

How do I write tests that verify code keeps its promises across APIs and services?▼

To verify code keeps its promises, write contract tests and invariant tests that validate API and service behaviors, ensuring critical failure modes and end-to-end workflows are checked.

What types of tests should I implement to prevent regressions in domain logic?▼

To prevent regressions in domain logic, implement regression tests alongside failure flow and invariant tests, ensuring software reliably fulfills its core contracts and handles critical failures.

Does this testing strategy require seeding data directly into the database?▼

Yes, this testing strategy requires seeding data directly into the database and utilizing seed helpers to establish consistent initial states for integration and end-to-end test workflows.

Why should I avoid test-coverage chasing when building test automation?▼

You should avoid test-coverage chasing because it often leads to naive tests; a principled framework focuses on critical failure modes, invariants, and integration quality instead.

Related Skills

Explore More Software Engineering Skills→
cyberAlchemyAIcyberAlchemyAI
20

invoke

Convert development intent into governed lifecycle artifacts with mode contracts.

Official
Advanced
mvillmowmvillmow
18

run-tests

Execute Mojo or Pytest test suites and generate structured pass/fail reports.

Community
Intermediate
bejranondabejranonda
27

testing-strategies

Define test coverage targets and organize unit, integration, and end-to-end tests.

Community
Basic
LuohaothuLuohaothu
24

test-coverage

Analyze coverage reports and flag files below the 80% threshold.

Community
Advanced