e2e-testing

Name: e2e-testing
Availability: InStock
Author: Tolki

Design and execute step-based end-to-end tests for Ghost.

5|Updated Feb 24, 2026

Search Tags:#automation #testing #debugging #e2e #fixtures #transcripts #harness

Ready to run

npx skills add https://github.com/mrtolkien/GHOST --skill e2e-testing-mrtolkien

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/mrtolkien/GHOST/tree/main/.agents/skills/e2e-testing
Command: npx skills add https://github.com/mrtolkien/GHOST --skill e2e-testing-mrtolkien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end testing workflows are complex and brittle; this skill provides a structured, step-based approach to design, run, and iterate tests that chain fixtures, manage snapshots, and produce reproducible results.

Core Features & Use Cases

Step-based E2E harness for Ghost test flows, fixtures, and snapshots.
Reusable scenario modules and harness steps with predecessor snapshot loading.
Artifacts and dashboards: workspace state, transcripts, metrics to support debugging and iteration.
Use Case: Debug failing end-to-end tests, rewrite tests, and verify behavior across model aliases.

Quick Start

Boot the e2e-testing workflow and begin creating and iterating end-to-end test steps for Ghost.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema

How do I structure end-to-end tests that chain fixtures across multiple steps?▼

To structure end-to-end tests that chain fixtures, you can use a step-based harness that loads predecessor snapshots sequentially. This isolates each step while passing state forward to maintain reproducible results across the test flow.

What is the best way to debug failing e2e tests and verify behavior across model aliases?▼

The best way to debug failing e2e tests is using structured artifacts like workspace state, transcripts, and metrics. These outputs support iteration and help verify behavior when running tests sequentially across multiple model aliases.

How do I manage LiveTestEnv snapshots and ensure step isolation during e2e testing?▼

Managing LiveTestEnv snapshots requires a harness that supports predecessor snapshot loading for step isolation. This approach ensures each test step starts from a known state and automatically triggers rollback after failures.

Can I run e2e tests sequentially across multiple model aliases for Ghost test flows?▼

Yes, you can run e2e tests sequentially across multiple model aliases for Ghost test flows. The harness design supports scenario modules that execute step-by-step while maintaining structured artifacts for each alias configuration.

Why do my end-to-end tests become brittle and how can a step-based harness help?▼

End-to-end tests become brittle due to complex state dependencies, but a step-based harness solves this by isolating steps and managing fixture chaining. It produces reproducible results through structured workspace state and automated rollback after failures.