e2e-test

Create, execute, and document Playwright end-to-end UI journey tests with GIF recording.

35|9|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/Appsilon/mediforce --skill e2e-test-appsilon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-test
Source: https://github.com/Appsilon/mediforce/tree/main/skills/e2e-test
Command: npx skills add https://github.com/Appsilon/mediforce --skill e2e-test-appsilon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end journey testing is essential for validating UI features, but writing, running, and documenting reliable tests—along with sharing visual results—can be time-consuming and error-prone without a repeatable process.

Core Features & Use Cases

  • End-to-end Journey Tests: Create a single feature-focused test per user journey using Playwright, with clear structure and expectations.
  • Recording & Documentation: Automatically record GIFs of test runs and maintain a gallery for quick QA and stakeholder reviews.
  • Guided Template & Helpers: Use the provided journey template and helpers (setupRecording, click, showStep, showResult, endRecording) to standardize tests and capture meaningful interactions.
  • Test Data Isolation: Add dedicated seed data in e2e/helpers/seed-data.ts to ensure tests run against isolated, reproducible environments without mutating shared data.
  • Running & Debugging: Execute targeted tests with pnpm commands and use the GIF workflow to verify outcomes in CI or local development.

Quick Start

Create a new journey file under packages/platform-ui/e2e/journeys following the template, then run the appropriate pnpm test:e2e command for your environment.

Frequently Asked Questions about e2e-test

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

FAQPage Schema
How do I automate end-to-end UI tests with Playwright?

Automate end-to-end UI tests with Playwright by creating a single feature-focused test file per user journey, utilizing structured helper utilities like setupRecording, click, showStep, and endRecording to standardize interactions and validate frontend features.

Can I record GIFs of Playwright test runs for QA reviews?

Yes, you can record GIFs of Playwright test runs for QA reviews. The process automatically captures visual recordings of test executions and maintains a gallery, enabling quick visual verification and stakeholder reviews in CI or local development environments.

How do I ensure repeatable E2E tests without mutating shared data?

Ensure repeatable E2E tests without mutating shared data by adding dedicated seed data within the e2e/helpers/seed-data.ts file. This test data isolation guarantees tests run against isolated, reproducible environments for reliable, auditable outcomes.

What is the best way to structure regression testing for frontend feature validation?

The best way to structure regression testing for frontend feature validation is using a guided journey template. This standardizes end-to-end tests by applying clear expectations, helper utilities, and isolated seed data for consistent, repeatable test coverage.

Does this E2E testing approach support running targeted tests in CI?

Yes, this E2E testing approach supports running targeted tests in CI. You execute specific tests using pnpm commands and leverage the GIF recording workflow to verify outcomes, ensuring reliable regression testing and visual documentation of UI journeys.

Why do my end-to-end journey tests fail to produce reproducible environments?

End-to-end journey tests fail to produce reproducible environments when they mutate shared data. Resolve this by using dedicated seed data files in e2e/helpers/seed-data.ts to isolate test environments and ensure consistent, repeatable test execution.