skills.rest
KentoShimizu
KentoShimizuCOMMUNITY
Explore all skills by this author →
𝕏@KStartup_GitHub

testing-integration

Integrates otherwise separate modules by testing seams and validating contracts with reproducible fixtures and CI-ready outputs.

7|Updated Feb 14, 2026
Search Tags:#integration#system-architecture#ci-cd#boundary-testing#reproducible-tests#seam
One-click install
npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill testing-integration-kentoshimizu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-integration
Source: https://github.com/KentoShimizu/sw-agent-skills/tree/main/skills/testing-integration
Command: npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill testing-integration-kentoshimizu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Integration testing across module boundaries to ensure the whole system behaves correctly when combined.

Core Features & Use Cases

  • Boundary enumeration and risk assessment
  • Reproducible seam-level tests with fixture strategies
  • Evidence and ownership documentation for CI integration
  • Use Case: verify message passing between services and adapter replacements without breaking contracts

Quick Start

Run a seam-focused integration test suite against your service topology.

Frequently Asked Questions about testing-integration

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

FAQPage Schema
How do I test integration seams across interdependent modules?▼

Testing integration seams involves identifying and validating boundary behavior across interdependent modules to ensure the whole system behaves correctly when combined. You define integration contracts and apply reproducible seam-level tests against your service topology.

What is boundary enumeration and when do I need it for API boundaries?▼

Boundary enumeration is the process of identifying and assessing risks at integration seams like API boundaries or event-driven flows. You need it when verifying data exchange between components to ensure adapters and message passing do not break existing contracts.

How do I create reproducible integration tests for CI pipelines?▼

Create reproducible integration tests by defining fixture strategies and integration contracts that produce evidence-ready outputs. These outputs are designed for CI integration, allowing you to run seam-focused test suites against your service topology automatically.

Can I use this approach for event-driven flows and data exchange between components?▼

Yes, this approach applies to scenarios where integration seams matter, including event-driven flows and data exchange between components. It verifies message passing between services and validates adapter replacements without breaking defined contracts.

What is the best way to verify message passing between services without breaking contracts?▼

The best way is to define integration contracts and apply reproducible seam-level tests with fixture strategies. This verifies message passing between services and adapter replacements while generating ownership documentation for CI integration.

Related Skills

Explore More Software Engineering Skills→
KohlexKohlex

architecture-design

Generate an ARCHITECTURE.md design contract from WEDGE-AND-CAPABILITIES.md, capabilities.yaml, and PRD.

Official
Advanced
mahg-esmahg-es
3

compliance

Map regulatory requirements to technical controls and automate evidence collection.

Official
Advanced
jorgeochipinti97jorgeochipinti97

testing-strategy

Define a hexagonal-layer testing strategy with Vitest, Playwright, and Pact.

Community
Advanced
farmountainfarmountain
1

E2E Test Runner

Execute end-to-end tests to validate complete user workflows across the application stack.

Community
Advanced