skills.rest
slusset
slussetCOMMUNITY
Explore all skills by this author →
GitHub

e2e-journey-testing

Translate user journeys into executable Playwright end-to-end tests.

1|Updated Feb 8, 2026
Search Tags:#automation#testing#e2e#playwright#specs#journey-testing
One-click install
npx skills add https://github.com/slusset/intention-driven-design --skill e2e-journey-testing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-journey-testing
Source: https://github.com/slusset/intention-driven-design/tree/main/skills/e2e-journey-testing
Command: npx skills add https://github.com/slusset/intention-driven-design --skill e2e-journey-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate user journeys into executable end-to-end tests to ensure the entire experience works as designed across frontend and backend.

Core Features & Use Cases

  • Journey-to-test translation: converts specs/journeys and specs/journey-maps into runnable Playwright tests.
  • Support utilities: provides fixtures, auth helpers, and API stubs to simplify test authoring.
  • Traceability and maintainability: guarantees tests reference journey, map, stories, and features; tests are independent and repeatable.

Quick Start

Create an e2e journey test by mapping a narrative to a Playwright spec in frontend.

Frequently Asked Questions about e2e-journey-testing

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

FAQPage Schema
How do I translate user journeys into executable Playwright tests?▼

To translate user journeys into Playwright tests, the Skill consumes narrative specs and journey maps to generate runnable frontend specs. It maps the provided journey references directly into deterministic test code.

What do I need to generate e2e tests from journey maps?▼

Generating e2e tests from journey maps requires narrative and map references, specifically specs/journeys and specs/journey-maps. You also need the frontend environment to produce the Playwright specs.

Can I use fixtures and route mocks for independent Playwright testing?▼

Yes, you can use fixtures and route mocks for independent Playwright testing. The Skill produces deterministic, isolated tests by utilizing support modules, API stubs, and route mocks.

Why should I use journey maps for automated e2e testing?▼

Using journey maps for automated e2e testing ensures traceability and maintainability across frontend and backend. It guarantees that generated tests explicitly reference journey narratives, stories, and features.

Does e2e journey testing work without backend dependencies?▼

e2e journey testing works without live backend dependencies by using route mocks and API assertions. The Skill incorporates support utilities and API stubs to produce repeatable, independent tests.

What is the best way to automate frontend specs from narrative specs?▼

The best way to automate frontend specs from narrative specs is to map the journey definitions to executable Playwright tests. This approach ensures the tests are deterministic and reference the original features.

Related Skills

Explore More Software Engineering Skills→
slussetslusset
1

angular-playwright

Automate Angular end-to-end tests with Playwright narrative-driven specs.

Community
Advanced
drvossdrvoss
42

e2e-testing

Generate Playwright or Cypress end-to-end test suites for critical user journeys.

Community
Advanced
jtvarisjtvaris

test-data-factory

Generate deterministic .fixture() extensions and builders for Swift model types.

Community
Advanced
thktthkt
11

e2e

Generate Playwright E2E tests and documentation through guided browser interactions.

Community
Intermediate