mcpField
E
end-to-end-testing

end-to-end-testing

github.com/aws-samplesTesting & quality5350 installsUpdated 9w ago
Repository

About end-to-end-testing

A structured end-to-end testing skill for teams validating full system behavior. It guides preparation, test execution, evidence checks, and report generation.

Key features

  1. 01Staged E2E testing workflow
  2. 02Test case planning and prioritization
  3. 03Screenshot and log evidence capture
  4. 04Pre-report evidence validation
  5. 05HTML and Markdown reports

Use cases

  1. 01Validating complete user flows
  2. 02Recording evidence during integration tests
  3. 03Checking defect records before reporting
  4. 04Archiving test results for review

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/aws-samples/sample-agent-skills-for-builders --skill end-to-end-testing

After installing, type/end-to-end-testingin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

README.md
assets/templates/
defect-report.md
Test_Report_Viewer.html
test-case-report.md
test-env.template
test-summary-report.md
references/
execution.md
planning-design.md
preparation.md
reporting.md
validation.md
scripts/
generate-html-report.py
validate-test-data.sh

Details

From the project README

End-to-End Testing

Systematic E2E testing workflow for complete system validation with evidence capture.

When to Apply

Reference this skill when:

  • Running integration or E2E tests
  • Validating complete user flows
  • Capturing test evidence (screenshots, logs)
  • Generating test reports
  • Documenting defects systematically

How It Works

Phase 1: Preparation
  • Gather environment information
  • Verify test credentials
  • Set up test data
Phase 2: Planning & Design
  • Smoke testing
  • Test case design
  • Priority assignment
Phase 3: Execution
  • Execute test cases
  • Capture evidence (screenshots)
  • Document defects
Phase 4: Pre-Reporting Validation (CRITICAL)
  • MANDATORY before reporting
  • Verify all evidence captured
  • Validate defect documentation
  • Cross-check test results
Phase 5: Reporting
  • Generate comprehensive reports
  • Create HTML viewer
  • Archive evidence

Output Structure

test-reports/
└── YYYY-MM-DD_HHMMSS/
    ├── Test_Report_Viewer.html
    ├── test-case-reports/
    ├── defect-reports/
    ├── test-summary-report.md
    ├── screenshots/
    └── logs/

Usage

# Generate HTML report
python scripts/generate-html-report.py --input test-results/

# Validate test data
./scripts/validate-test-data.sh

Templates

References

Comments

Markdown supported