agentsclimarketplace
Sign in

Testing integration

Skill planifest/planifest-framework/planifest-framework/external-skills/testing-integration

Integration-boundary testing for component and service collaboration correctness. Use when modules interact via APIs, queues, databases, or adapters and boundary behavior must be verified; do not use for full UI journey validation or pure unit isolation work.From its SKILL.md

Install
npx -y skills add planifest/planifest-framework --skill testing-integration

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 330 tokens by cl100k_base, as published. Nobody here has run it

Testing Integration

Overview

Use this skill to verify boundary behavior where independently correct units may still fail in combination.

Scope Boundaries

  • Use when correctness depends on integration seams.
  • Typical requests:
    • Validate repository-to-database behavior including failure paths.
    • Test timeout and retry handling between services.
    • Verify adapter replacement does not break boundary contracts.
  • Do not use when:
    • The goal is full browser journey validation (testing-e2e/playwright).
    • The goal is pure isolated unit checks (testing-unit).

Inputs

  • Integration seams and dependency topology
  • Failure-mode expectations (timeout, retry, partial failure)
  • Fixture/environment constraints

Outputs

  • Boundary test matrix with dependency strategy
  • Decision record for integration depth and tooling choices
  • Verification checklist for success and failure semantics

Workflow

  1. Enumerate high-risk seams and boundary contracts.
  2. Define required behaviors for success, timeout, and error cases.
  3. Compare fixture strategies and choose one with rationale.
  4. Execute focused integration tests with reproducible setup.
  5. Publish coverage gaps, residual risks, and ownership.

Quality Gates

  • Critical seams include failure-path coverage.
  • Boundary expectations are explicit and deterministic.
  • Evidence can be replayed in CI.
  • Dependency assumptions are documented.

Failure Handling

  • Stop when critical boundaries lack failure-path tests.
  • Escalate when dependency ownership blocks reliable fixtures.

Bundled Resources

  • references/trigger-and-examples.md: trigger patterns, anti-patterns, and deliverable expectations.

What ships with it: 1 file

11.3 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,750. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.