running-e2e-tests
Execute end-to-end tests covering full user workflows across frontend and backend.Use when performing specialized testing.Trigger with phrases like "run end-to-end tests", "test user flows", or "execute E2E suite".
When & Why to Use This Skill
This Claude skill automates the execution and analysis of end-to-end (E2E) tests, validating complete user workflows across both frontend and backend systems. It streamlines the testing lifecycle by preparing environments, running test suites via bash commands, analyzing results for patterns, and generating detailed performance reports to ensure software reliability and quality.
Use Cases
- Automated Regression Testing: Run full E2E suites after code changes to ensure existing user workflows remain intact and bug-free.
- Pre-release Validation: Execute comprehensive 'smoke tests' across the entire stack before deploying new features to production environments.
- Continuous Integration (CI) Support: Integrate with development pipelines to automatically trigger tests and generate insights on success rates and performance bottlenecks.
- Cross-Stack Debugging: Identify failures in complex interactions between frontend UI components and backend API services through detailed error analysis and stack traces.
| name | running-e2e-tests |
|---|---|
| version | 1.0.0 |
| description | | |
| allowed-tools | Read, Write, Edit, Grep, Glob, Bash(test:e2e-*) |
| license | MIT |
Prerequisites
Before using this skill, ensure you have:
- Test environment configured and accessible
- Required testing tools and frameworks installed
- Test data and fixtures prepared
- Appropriate permissions for test execution
- Network connectivity if testing external services
Instructions
Step 1: Prepare Test Environment
Set up the testing context:
- Use Read tool to examine configuration from {baseDir}/config/
- Validate test prerequisites are met
- Initialize test framework and load dependencies
- Configure test parameters and thresholds
Step 2: Execute Tests
Run the test suite:
- Use Bash(test:e2e-*) to invoke test framework
- Monitor test execution progress
- Capture test outputs and metrics
- Handle test failures and error conditions
Step 3: Analyze Results
Process test outcomes:
- Identify passed and failed tests
- Calculate success rate and performance metrics
- Detect patterns in failures
- Generate insights for improvement
Step 4: Generate Report
Document findings in {baseDir}/test-reports/:
- Test execution summary
- Detailed failure analysis
- Performance benchmarks
- Recommendations for fixes
Output
The skill generates comprehensive test results:
Test Summary
- Total tests executed
- Pass/fail counts and percentage
- Execution time metrics
- Resource utilization stats
Detailed Results
Each test includes:
- Test name and identifier
- Execution status (pass/fail/skip)
- Actual vs. expected outcomes
- Error messages and stack traces
Metrics and Analysis
- Code coverage percentages
- Performance benchmarks
- Trend analysis across runs
- Quality gate compliance status
Error Handling
Common issues and solutions:
Environment Setup Failures
- Error: Test environment not properly configured
- Solution: Verify configuration files; check environment variables; ensure dependencies are installed
Test Execution Timeouts
- Error: Tests exceeded maximum execution time
- Solution: Increase timeout thresholds; optimize slow tests; parallelize test execution
Resource Exhaustion
- Error: Insufficient memory or disk space during testing
- Solution: Clean up temporary files; reduce concurrent test workers; increase resource allocation
Dependency Issues
- Error: Required services or databases unavailable
- Solution: Verify service health; check network connectivity; use mocks if services are down
Resources
Testing Tools
- Industry-standard testing frameworks for your language/platform
- CI/CD integration guides and plugins
- Test automation best practices documentation
Best Practices
- Maintain test isolation and independence
- Use meaningful test names and descriptions
- Keep tests fast and focused
- Implement proper setup and teardown
- Version control test artifacts
- Run tests in CI/CD pipelines