How do I install the Testing E2e skill?

Run npx skillmds@latest add planifest/testing-e2e in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Testing E2e safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Testing E2e?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Testing E2e free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Testing E2e?

planifest (@planifest) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Testing E2e by planifest — Agent Skill

Name: Testing E2e
Author: planifest

Testing E2e

End-to-end test planning for critical user journeys across integrated systems. Use when release confidence depends on browser/API/dependency behavior as one flow; do not use for isolated unit behavior or pure contract checks.

planifest 7dbb830 2 files · 13.4 KB Updated Sep 17, 2026

File contents

Testing E2E

Overview

Use this skill to validate business-critical journeys under integrated runtime conditions.

Scope Boundaries

Use when failure risk is in end-to-end user or operator flows.
Typical requests:
- Validate checkout flow across UI, API, and payment integration.
- Define minimum critical E2E regression set before release.
- Prove no fatal breakage in top user journeys.
Do not use when:
- Only deterministic function logic must be tested (testing-unit).
- Only interface compatibility is required (testing-contract).

Inputs

Critical journey map and release risk profile
Test environment constraints and dependencies
Existing automation assets and known flaky areas

Outputs

Critical journey E2E pack with environment assumptions
Decision record for coverage depth and gating strategy
Verification checklist and rollback signals

Workflow

Identify journeys that gate release confidence.
Define minimum E2E set by risk and business impact using assets/critical-journey-template.md.
Compare execution strategies (full, smoke, tiered) and choose one.
Implement deterministic setup/teardown and evidence capture.
Publish pass/fail status, flake risk, and residual gaps.

Quality Gates

Critical journeys are explicitly covered.
Test evidence is reproducible with fixed environment assumptions.
Gating and rollback signals are defined.
Flakiness and environment risks are documented.

Failure Handling

Stop when critical journeys remain untested.
Escalate when environment instability prevents reliable evidence.

Bundled Resources

references/trigger-and-examples.md: trigger patterns, anti-patterns, and deliverable expectations.
assets/critical-journey-template.md: concise template for critical-path E2E scenario definition and evidence capture.

---name: testing-e2edescription: End-to-end test planning for critical user journeys across integrated systems. Use when release confidence depends on browser/API/dependency behavior as one flow; do not use for isolated unit behavior or pure contract checks.---# Testing E2E## OverviewUse this skill to validate business-critical journeys under integrated runtime conditions.## Scope Boundaries- Use when failure risk is in end-to-end user or operator flows.- Typical requests: - `Validate checkout flow across UI, API, and payment integration.` - `Define minimum critical E2E regression set before release.` - `Prove no fatal breakage in top user journeys.`- Do not use when: - Only deterministic function logic must be tested (`testing-unit`). - Only interface compatibility is required (`testing-contract`).## Inputs- Critical journey map and release risk profile- Test environment constraints and dependencies- Existing automation assets and known flaky areas## Outputs- Critical journey E2E pack with environment assumptions- Decision record for coverage depth and gating strategy- Verification checklist and rollback signals## Workflow1. Identify journeys that gate release confidence.2. Define minimum E2E set by risk and business impact using `assets/critical-journey-template.md`.3. Compare execution strategies (full, smoke, tiered) and choose one.4. Implement deterministic setup/teardown and evidence capture.5. Publish pass/fail status, flake risk, and residual gaps.## Quality Gates- Critical journeys are explicitly covered.- Test evidence is reproducible with fixed environment assumptions.- Gating and rollback signals are defined.- Flakiness and environment risks are documented.## Failure Handling- Stop when critical journeys remain untested.- Escalate when environment instability prevents reliable evidence.## Bundled Resources- `references/trigger-and-examples.md`: trigger patterns, anti-patterns, and deliverable expectations.- `assets/critical-journey-template.md`: concise template for critical-path E2E scenario definition and evidence capture.

Frequently asked questions