← Browse

@francostino/e2e-testing-patterns

A

Build reliable, fast, and maintainable end-to-end test suites that provide confidence to ship code quickly and catch regressions before users do.

skillclaude

Install

agr install @francostino/e2e-testing-patterns --target claude

Writes 1 file into .claude/skills/, pinned to git-79bbbe1b.

  • .claude/skills/e2e-testing-patterns/SKILL.md

Document


name: e2e-testing-patterns description: "Build reliable, fast, and maintainable end-to-end test suites that provide confidence to ship code quickly and catch regressions before users do." risk: safe source: community date_added: "2026-02-27"

E2E Testing Patterns

Build reliable, fast, and maintainable end-to-end test suites that provide confidence to ship code quickly and catch regressions before users do.

Use this skill when

  • Implementing end-to-end test automation
  • Debugging flaky or unreliable tests
  • Testing critical user workflows
  • Setting up CI/CD test pipelines
  • Testing across multiple browsers
  • Validating accessibility requirements
  • Testing responsive designs
  • Establishing E2E testing standards

Do not use this skill when

  • You only need unit or integration tests
  • The environment cannot support stable UI automation
  • You cannot provision safe test accounts or data

Instructions

  1. Identify critical user journeys and success criteria.
  2. Build stable selectors and test data strategies.
  3. Implement tests with retries, tracing, and isolation.
  4. Run in CI with parallelization and artifact capture.

Safety

  • Avoid running destructive tests against production.
  • Use dedicated test data and scrub sensitive output.

Resources

  • resources/implementation-playbook.md for detailed E2E patterns and templates.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-79bbbe1b2bfa2026-07-31