e2e-testing

Run JSON-based end-to-end tests against ikigai's control socket.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/mgreenly/ikigai --skill e2e-testing-mgreenly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/mgreenly/ikigai/tree/main/.claude/library/e2e-testing
Command: npx skills add https://github.com/mgreenly/ikigai --skill e2e-testing-mgreenly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

JSON-based end-to-end tests verify ikigai behavior through its control socket, enabling repeatable, deterministic validation of UI and backend flows.

Core Features & Use Cases

  • Self-contained JSON test definitions including name, steps, and assertions
  • Run tests in mock mode using a mock provider or in live mode with real providers
  • Organize tests in tests/e2e/ with a defined execution order in tests/e2e/index.json

Quick Start

Place JSON test files in tests/e2e and run the built-in runner to execute them in mock or live mode.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema
How do I automate end-to-end testing for ikigai workflows?

End-to-end testing for ikigai workflows is automated by validating control socket interactions through JSON-based test definitions. You define structured test suites with specific steps and assertions, then execute them using a built-in runner in either mock or live mode.

What is the JSON schema for writing ikigai end-to-end tests?

The JSON schema for ikigai end-to-end tests enforces four fixed fields: name, steps, assert, and assert_mock. Test files are self-contained definitions placed in the tests/e2e directory to validate UI and backend flows deterministically.

What step types are supported in JSON-based e2e test runners?

Supported step types in JSON-based e2e test runners include send_keys, read_framebuffer, wait, wait_idle, and mock_expect. These steps define the sequence of control socket interactions and mock behaviors for validating application behavior.

Can I run end-to-end tests in mock mode without real providers?

End-to-end tests can run in mock mode using a mock provider to validate behavior without real providers. This enables repeatable, deterministic testing of UI and backend flows by intercepting control socket interactions with predefined mock expectations.

How do I define the execution order for an e2e test suite?

Execution order for an e2e test suite is defined by the tests/e2e/index.json file. This file organizes the sequence of self-contained JSON test definitions stored in the tests/e2e directory for systematic validation.