Integration testing

Skill lubochka/xiigen-general-skills/codex/skills/integration-testing

Verify boundaries between components. Use when behavior crosses services, modules, tools, adapters, or data formats.From its SKILL.md

Install

npx -y skills add lubochka/xiigen-general-skills --skill integration-testing

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

1 stars1 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

0.9 KB, 147 tokens by cl100k_base, as published. Nobody here has run it

Integration Testing

Purpose

Verify boundaries between components.

When to Use

Use when behavior crosses services, modules, tools, adapters, or data formats.

Inputs

Component boundary, contract, realistic inputs, target project commands.

Steps

Identify the integration boundary.
Define realistic inputs and expected outputs.
Run or design the narrowest useful integration test.
Record unsupported dependencies or blockers.

Gates

At least one meaningful boundary scenario is covered or blocked.

Evidence

Integration test output, contract check, or explicit blocker.

Anti-Patterns

Replacing integration coverage with isolated unit tests only.

test-integrity, e2e-test-matrix

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most test skills give in 147 tokens

Counted across 964 of the 1,571 authors here whose files we hold, read 2026-08-07

Close the browser when donein 55 of 964, across 12 files
Wait for network idle statein 51 of 964, across 6 files
Launch Chromium in headless modein 49 of 964, across 6 files
Use descriptive selectors for elementsin 49 of 964, across 6 files
Run provided scripts with help flag firstin 49 of 964, across 6 files
Add appropriate explicit waitsin 48 of 964, across 5 files
Use bundled scripts as black boxesin 46 of 964, across 3 files
Do not read script source codein 46 of 964, across 3 files
Use sync playwright for scriptsin 46 of 964, across 3 files
Inspect dom before executing actionsin 46 of 964, across 3 files
Run the full test suitein 37 of 964
Write the failing test firstin 29 of 964, across 23 files

Said here and by no other author read

define realistic inputs and expected outputs
run the narrowest useful integration test
record unsupported dependencies or blockers
cover at least one meaningful boundary scenario

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.