Back to Skills

E2e Testing Patterns

Skills development 110 Scanned by NVIDIA SkillSpector

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

Install Command
npx claude-code-templates@latest --skill development/e2e-testing-patterns
View on GitHub
claude-code — e2e-testing-patterns

Scanned by NVIDIA SkillSpector

Automated static analysis (no LLM) · v2.12.0 · 2026-10-24

Partial analysis: some checks could not run on this component.

5 observations
scanner score 37/100

SkillSpector looks for patterns such as shell commands, credential access, network calls or unpinned dependencies. An observation is something worth reading in the files before you install, not a confirmed vulnerability. Components that run code locally, like hooks, MCP servers and security tooling, naturally show more of them.

  • Incomplete referenced artifact analysis
    analysis-evasion · SKILL.md:45
  • npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update. ×4
    MCP Rug Pull · resources/implementation-playbook.md:429

Learn more about NVIDIA SkillSpector.

Content

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.

Stack Builder

0 components

Your stack is empty

Browse components and click the + button to add them to your stack for easy installation.