skills.rest
jivebreaddev
jivebreaddevCOMMUNITY
Explore all skills by this author →
GitHub

testing

Classify test cases into Unit, Integration, Concurrency, Adapter, and E2E skeletons.

Updated Feb 5, 2026
Search Tags:#testing#tdd#integration-test#unit-test#e2e-test#concurrency-test#adapter-test
One-click install
npx skills add https://github.com/jivebreaddev/skills-claude-agent --skill testing-jivebreaddev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/jivebreaddev/skills-claude-agent/tree/main/.claude/projects/loopers-kotlin-spring-template/skills/testing
Command: npx skills add https://github.com/jivebreaddev/skills-claude-agent --skill testing-jivebreaddev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides teams to enforce disciplined testing practices, preventing interaction-based verifications and focusing on observable state outcomes.

Core Features & Use Cases

  • Enforces Classical TDD principles across unit, integration, concurrency, adapter, and end-to-end testing.
  • Provides reference-driven patterns and structure for test skeletons.
  • Helps classify test cases by responsibility and ensure proper factory methods and isolation.

Quick Start

Provide comprehensive testing skeletons that reflect kingdom of test levels, with clear Given/When/Then framing and no use of verify().

Frequently Asked Questions about testing

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

FAQPage Schema
How do I enforce Classical TDD and stop using interaction verifications in unit tests?▼

To enforce Classical TDD, you prevent interaction-based verifications and guide state-based assertions, ensuring tests reflect observable outcomes rather than implementation details.

What is the correct way to classify test cases into Unit, Integration, and E2E levels?▼

Classifying test cases involves applying test-level guidelines to sort responsibilities into Unit, Integration, Concurrency, Adapter, and E2E levels, producing focused skeletons with proper structure.

How do I structure test skeletons using Given/When/Then framing for TDD?▼

You structure test skeletons by applying test-level guidelines to produce focused structures with clear Given/When/Then framing, utilizing factory-method patterns to ensure proper isolation.

When should I write concurrency tests and adapter tests instead of standard unit tests?▼

Write concurrency tests and adapter tests instead of standard unit tests when test-level guidelines classify specific cases as requiring these structures to verify observable outcomes accurately.

Why does my test suite break when refactoring implementation details?▼

Your test suite breaks during refactoring because tests rely on interaction verifications rather than observable state outcomes, making them fragile to internal implementation changes.

Related Skills

Explore More Software Engineering Skills→
vlad-ryzhkovvlad-ryzhkov
25

repo-scout

Audit Go backend repositories for API endpoints, infrastructure, and test coverage.

Community
Intermediate
BerryKuipersBerryKuipers
7

validate-coverage-threshold

Validate JavaScript/TypeScript test coverage against configured thresholds from coverage reports.

Community
Intermediate
benredmondbenredmond
3

ship

Coordinate adversarial review, commits, and reflections to finalize APEX tasks.

Community
Advanced
ayehiaaayehiaa

tdd

Apply test-driven development through red-green-refactor cycles with behavior-focused integration tests.

Community
Intermediate