test-e2e

Included with Lifetime

$97 forever

Execute end-to-end test specification and report results. Use after implementation to validate user journeys before review.

Code Review

What this skill does


# E2E Test Runner

Execute an end-to-end test specification and report results.

## Variables

- `e2e_test_file`: $1 - Path to the E2E test specification file

## Instructions

1. **Read the Test Specification**: Load and parse the e2e_test_file
2. **Digest the User Story**: Understand what user journey is being tested
3. **Execute Test Steps**: Perform each step in sequence
4. **Verify Checkpoints**: Check all `**Verify**` steps carefully
5. **Capture Screenshots**: Save screenshots as specified in the test
6. **Report Results**: Return structured JSON output

## Execution Process

For each step in the test specification:

1. Read the step instruction
2. Execute the action (navigate, click, enter, etc.)
3. If step contains `**Verify**`:
   - Check the condition
   - If fails, mark test as failed and stop
4. If step says "Take screenshot":
   - Capture current state
   - Save to screenshots directory

## Success Criteria Validation

After all steps complete:

- Review the Success Criteria section
- Verify each criterion is met
- If any criterion fails, mark test as failed

## Output Format

Return ONLY a JSON object:

**Passed:**

```json
{
  "test_name": "Basic Query Execution",
  "status": "passed",
  "screenshots": [
    "screenshots/01_initial_state.png",
    "screenshots/02_query_input.png",
    "screenshots/03_results.png"
  ],
  "error": null
}
```

**Failed:**

```json
{
  "test_name": "Basic Query Execution",
  "status": "failed",
  "screenshots": [
    "screenshots/01_initial_state.png",
    "screenshots/02_query_input.png"
  ],
  "error": "Step 8 failed: Results did not appear within 5 seconds"
}
```

## Result Structure

| Field | Description |
| --- | --- |
| `test_name` | Name from the test specification |
| `status` | "passed" or "failed" |
| `screenshots` | Array of screenshot paths captured |
| `error` | Error description if failed, null if passed |

## Integration with Closed Loop

This command is the **REQUEST** phase for E2E validation:

```text
/test-e2e {spec} → [JSON result] → /resolve-failed-e2e-test {result}
```

## Example Usage

```text
/test-e2e .claude/commands/e2e/test-basic-query.md
```

Files: 1

Size: 2.3 KB

Complexity: 10/100

Category: Code Review

Source: https://github.com/melodic-software/claude-code-plugins/tree/main/plugins/tac/skills/test-e2e

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts