integration-tests

Convert enabled design specifications into traceable integration test cases and verification results.

15|5|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/sohei56/maul-team --skill integration-tests-sohei56
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration-tests
Source: https://github.com/sohei56/maul-team/tree/main/skills/integration-tests
Command: npx skills add https://github.com/sohei56/maul-team --skill integration-tests-sohei56

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents integration defects from reaching user acceptance and release by systematically converting enabled design specifications into executable, traceable tests.

Core Features & Use Cases

  • Design-Driven Coverage: Derives boundary-value, flow-branch, state-transition, decision-table, and external-integration test cases from the project's enabled specifications.
  • Automated Verification: Builds API tests, Playwright UI tests, and contract-faithful stubs for non-reproducible external services.
  • Quality-Gated Reporting: Records test verdicts, coverage, automation rates, skipped checks, and defects in Scrum artifacts before UAT and release.
  • Use Case: During an Integration Sprint, use this Skill to validate a completed product against its approved design specs, commit reusable test assets, and route failures to defect PBIs instead of fixing production code during testing.

Quick Start

Run the integration-tests skill during the Integration Sprint to derive, automate, execute, and report tests for every enabled design specification.

Frequently Asked Questions about integration-tests

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

FAQPage Schema
How do I turn design specifications into executable integration tests?

Integration testing validates completed products against approved design specs by deriving boundary-value, flow-branch, state-transition, and decision-table test cases. It systematically prevents integration defects from reaching user acceptance and release by verifying APIs, UI workflows, and business rules.

How do I generate API and Playwright UI tests from design specs during a sprint?

Generating API and Playwright UI tests from design specs requires applying the skill during an Integration Sprint. It builds automated API tests, Playwright UI tests, and contract-faithful stubs to verify enabled specifications against business rules and external services.

How do I create test stubs for external services that cannot be reproduced in testing?

To create test stubs for non-reproducible external services, you build contract-faithful stubs based on your enabled design specifications. This allows integration testing to proceed accurately without requiring live external service availability during the Integration Sprint.

Do I need Scrum state files to automate integration testing and report test verdicts?

Yes, you need Scrum state files and test-result recording scripts to automate integration testing and report verdicts. The skill records test verdicts, coverage, automation rates, and defects directly into Scrum artifacts before UAT readiness checks.

What is the best way to handle integration test failures without fixing production code during testing?

The best way to handle integration test failures is to route them to defect Product Backlog Items instead of fixing production code during testing. This quality-gated approach records skipped checks and defects in Scrum artifacts for proper sprint resolution.