integration-e2e-testing

A set of rules for writing and reviewing integration tests and end-to-end tests. Integration tests check multiple parts together, while end-to-end tests check the complete system from start to finish.

In plain words
What is it for?
Use it when implementing or reviewing integration and end-to-end tests, including their setup, assertions, mock usage, and execution conditions.
Why use it?
It helps ensure tests verify visible results and use mocks only at appropriate boundaries, so passing tests provide meaningful evidence.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/shinpr/agentic-code/integration-e2e-testing
Any agent
npx skills add shinpr/agentic-code --skill integration-e2e-testing
Clone the repo
git clone --depth 1 https://github.com/shinpr/agentic-code

Made for: Claude Code, Codex.

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 348 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00038 $0.00348
Opus 5 $0.00019 $0.00174
Sonnet 5 $0.00008 $0.00070
Haiku 4.5 $0.00004 $0.00035

Measured 2d ago against content hash f6ec68ea1434, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

integration-e2e-testing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/integration-e2e-testing/SKILL.md · 50 lines

What it actually says

Integration and E2E Test Implementation and Review Rules

Implementation Rules

Behavior Verification

Step Type Verification Target
Trigger Reproduce in test setup (Arrange)
Process Intermediate state or function call
Observable Result Final output value (return value, error message, log output)

Pass Criteria: Test passes if "observable result" is verified as return value or mock call argument

Integration Test Mock Boundaries

Judgment Criteria Mock Actual
Part of test target? No → Can mock Yes → Actual required
External network communication? Yes → Mock required No → Actual recommended

E2E Test Execution Conditions

  • Execute only after all components are implemented
  • Do not use mocks (full system integration required)

Review Criteria

Skeleton and Implementation Consistency

Check Failure Condition
Behavior Verification No assertion for "observable result"
Verification Item Coverage Listed verification items not included in assertions
Mock Boundary Internal components mocked in integration test

Implementation Quality

Check Failure Condition
AAA Structure Arrange/Act/Assert separation unclear
Independence State sharing between tests, execution order dependency
Reproducibility Depends on date/random, results vary
Readability Test name and verification content don't match
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 50 lines · 38 tokens per session scan A f6ec68ea1434

Subscribe to this mod's changes

integration-e2e-testing is a skill published in the GitHub repository shinpr/agentic-code (49 stars, last pushed 3d ago), licensed MIT. It adds 38 tokens to every session and 348 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.