test-e2e

Automate Playwright and CLI end-to-end test suite creation for Skaile-dev packages.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/skaile-ai/ai-assets --skill test-e2e-skaile-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-e2e
Source: https://github.com/skaile-ai/ai-assets/tree/main/skaile-development/skills/test-e2e
Command: npx skills add https://github.com/skaile-ai/ai-assets --skill test-e2e-skaile-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and validation of end-to-end test suites for Skaile-dev packages, including web Playwright tests and CLI-based tests, ensuring tests run against real dev servers or processes.

Core Features & Use Cases

  • Bootstraps Playwright-based E2E tests for forge apps, platform frontend, and the agent-framework CLI.
  • Generates CLI end-to-end tests that invoke binaries and assert stdout/artifacts.
  • Verifies tests run against a real dev server or process, with scaffolding for config, setup, teardown, and fixtures.

Quick Start

Run skaile add test-e2e to scaffold end-to-end tests for your target Skaile-dev package.

Frequently Asked Questions about test-e2e

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

FAQPage Schema
How do I generate end-to-end tests for Skaile-dev packages?

To generate end-to-end tests for Skaile-dev packages, run skaile add test-e2e to scaffold Playwright web tests and CLI test harnesses. The tool outputs scaffolding, config, setup, teardown, and fixtures to ensure tests run against real dev servers or processes.

What's the best way to automate Playwright test scaffolding for a forge app?

Automating Playwright test scaffolding for a forge app is done by applying the test-e2e suite, which bootstraps configuration and test templates. It reads relevant CLAUDE/docs to ensure real server verification and outputs complete web test setups.

Can I write CLI end-to-end tests that invoke binaries and assert stdout?

Yes, you can write CLI end-to-end tests that invoke binaries and assert stdout or artifacts. The test-e2e suite generates CLI test harnesses specifically for the agent-framework CLI, validating command-line interactions against real processes.

Does test-e2e support both web frontend and CLI testing workflows?

test-e2e supports both web frontend and CLI testing workflows by generating Playwright-based tests for platform frontends and CLI test harnesses for agent-frameworks. It provides scaffolding for config, setup, teardown, and fixtures across both testing types.

Do I need a real dev server running to validate end-to-end test suites?

Yes, a real dev server or process is required to validate end-to-end test suites. The generated scaffolding includes setup and teardown configurations specifically designed to verify that tests run against actual running dev servers or processes.

Why does my end-to-end test scaffolding need to read CLAUDE and docs files?

End-to-end test scaffolding reads CLAUDE and docs files to specify prerequisites and ensure accurate test generation. This approach allows the test-e2e suite to output templates that align with existing project configurations and real server verification requirements.