e2e

Name: e2e
Availability: InStock
Author: lepahc

Automate Playwright-based end-to-end tests for the kspec web UI.

1|2|Updated Jan 16, 2026

Search Tags:#automation #e2e #playwright #fixtures #ui-testing #daemon #kspec

Ready to run

npx skills add https://github.com/lepahc/kynetic-spec --skill e2e-lepahc

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

E2E testing patterns for the kspec web UI provide structured guidance for writing reliable Playwright tests, diagnosing hydration issues, and managing daemon fixtures during end-to-end validation.

Core Features & Use Cases

Isolated daemon and fixture setup per test to prevent cross-test contamination.
Robust selectors and interactions using ARIA roles and data-slot attributes for bits-ui components.
API request verification, URL navigation checks, and content assertions to validate end-to-end flows.
Clear guidance around fixture isolation, ULID considerations, and how to organize tests across unit and E2E suites.

Quick Start

Run Playwright-based E2E tests against the kspec web UI using the daemon fixture and isolated test fixtures.

Frequently Asked Questions about e2e

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

FAQPage Schema

How do I isolate Playwright E2E test fixtures to prevent cross-test contamination?▼

To isolate Playwright E2E test fixtures, you must configure isolated daemon and fixture setups for each test. This prevents cross-test contamination by ensuring daemon lifecycles and data remain completely independent across the kspec web UI validation suite.

What selectors should I use for Playwright tests on bits-ui components?▼

For Playwright tests on bits-ui components, you should use robust ARIA roles and data-slot attributes. These selectors provide reliable interaction targets, preventing flaky tests when validating UI flows within the kspec web application.

How do I debug hydration issues during Playwright E2E testing?▼

To debug hydration issues during Playwright E2E testing, apply structured diagnostic patterns for UI state mismatches. This involves verifying API requests with waitForRequest, checking URL navigations with waitForURL, and validating content assertions against daemon fixtures.

Why does my Playwright E2E test fail with invalid ULID references?▼

Your Playwright E2E test fails with invalid ULID references because ULID validity checks are a strict operational requirement. You must ensure ULID generation and validation are properly configured within your isolated test fixtures before running daemon interactions.

When should I separate unit testing fixtures from E2E daemon fixtures?▼

You should separate unit testing fixtures from E2E daemon fixtures when managing test isolation across different suite scopes. Organizing tests this way ensures E2E validations rely on daemon lifecycles while unit tests remain lightweight and independent.