e2e-next-test

Parse COVERAGE_PLAN.md to identify the next pending E2E test case.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/nebuladevops/skills-engineering-auto --skill e2e-next-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-next-test
Source: https://github.com/nebuladevops/skills-engineering-auto/tree/main/e2e-next-test
Command: npx skills add https://github.com/nebuladevops/skills-engineering-auto --skill e2e-next-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

E2E test writer for Scribe Nebula Medical (C:/NEBULA/proto_scribe). Your goal is to write tests that define expected product behavior, not tests that mirror current implementation.

Core Features & Use Cases

  • Reads tests/COVERAGE_PLAN.md to identify the next pending E2E case, prioritizes by priority and suite order.
  • Interacts with the user to capture expected UX behavior before reading source code.
  • Generates a Playwright test skeleton with mandatory annotation that reflects user input and coverage plan case details.

Quick Start

Run the companion script to fetch the next pending E2E test case, or specify a particular case with --case, or list pending cases with --list.

Frequently Asked Questions about e2e-next-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Playwright E2E test generation from a coverage plan?

Automating Playwright E2E test generation involves parsing a tests/COVERAGE_PLAN.md file to identify pending test cases, capturing expected UX behavior, and outputting an annotated test skeleton. This process extracts case details and prioritizes them by suite order for rapid test scaffolding.

What is a COVERAGE_PLAN.md file and how does it guide E2E test creation?

A COVERAGE_PLAN.md file defines pending E2E test cases prioritized by suite order and priority level. It guides E2E test creation by acting as a structured source for a companion script to parse, extract case details, and generate annotated Playwright test skeletons based on user expectations.

How do I list and select pending E2E test cases for Playwright test scaffolding?

Listing and selecting pending E2E test cases is done by running a companion script that reads the COVERAGE_PLAN.md file. You can use the --list flag to view pending cases or the --case flag to select a specific case for Playwright test scaffolding.

Can I filter E2E test cases by suite when generating Playwright test skeletons?

Filtering E2E test cases by suite is supported when generating Playwright test skeletons. The companion script reads the coverage plan and allows filtering by suite to guide test creation, ensuring the generated annotated skeleton reflects the selected suite's details and user expectations.

Does this E2E test generation approach require reading existing source code first?

E2E test generation using this approach does not require reading source code first. It interacts with the user to capture expected product behavior before reading source code, ensuring tests define expected UX behavior rather than mirroring current implementation.

Why should E2E tests define expected behavior instead of mirroring current implementation?

E2E tests should define expected behavior to validate actual product requirements rather than confirming existing code paths. This approach captures user-provided expectations before reviewing source code, generating Playwright skeletons that reflect intended UX behavior from the coverage plan.