Identify integration seams and guide end-to-end tests across modules, databases, and APIs.
npx skills add https://github.com/jonmumm/skills --skill seam-tester
Please help me install this Agent Skill. Skill: seam-tester Source: https://github.com/jonmumm/skills/tree/main/seam-tester Command: npx skills add https://github.com/jonmumm/skills --skill seam-tester
Seam-tester addresses the problem of brittle tests by prioritizing integration points where components, services, and APIs interact, ensuring end-to-end reliability.
Plan and execute your first seam test by selecting a cross-module workflow and validating the end-to-end interaction.
High-intent search queries and answers about installing and using this skill.
Integration testing at the seams targets cross-component interactions across modules, databases, external APIs, and file-system boundaries. You need it to ensure end-to-end reliability in multi-module architectures where component interactions are prone to failure.
Write resilient integration tests by minimizing internal mocking, focusing on observable outputs, and validating cross-module workflows deterministically. This keeps tests stable under internal refactors and system changes by verifying boundary interactions rather than internal implementations.
You should use minimal mocks of internal components during end-to-end system testing. Prioritize testing observable outputs at system seams to ensure tests remain stable and accurately reflect cross-component interactions during internal refactors.
Yes, seam testing is applicable to multi-module architectures with databases, external APIs, and file-system boundaries. It guides end-to-end and seam-level tests across services to validate cross-component consistency, such as verifying an order flow across microservices.
The best way to identify seams is to map cross-module workflows and isolate integration points between modules, databases, external APIs, and file-system boundaries. Explicit seam identification allows you to focus tests on observable outputs and deterministic scenarios.
Integration tests become brittle when they rely heavily on internal component mocking rather than observable outputs. Focus testing on system seams and cross-component interactions to ensure tests remain stable and deterministic under internal refactoring.
leogallegoDesigns Kotlin Multiplatform expect/actual boundaries separating shared code from platform implementations.
AhmedAbdelmoatyPlan and implement deterministic Playwright tests for browser apps and canvas games.
dcossonIdentifies vertical and horizontal mismatches across plan documents and outputs a structured seam-review artifact.
danielmichaelsGuide test-driven development for Rust and SQL codebases with DuckDB validation.
