e2e-testing

Document ikigai end-to-end test formats, runners, and mock providers.

Updated Mar 4, 2026

Search Tags:#automation #verification #e2e-testing #test-runner #mock-provider #json-tests #ikigai-ctl

Ready to run

npx skills add https://github.com/multicam/ikigai-rev --skill e2e-testing-multicam

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/multicam/ikigai-rev/tree/main/.claude-i/library/e2e-testing
Command: npx skills add https://github.com/multicam/ikigai-rev --skill e2e-testing-multicam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end testing verifies ikigai behavior through its control socket, ensuring consistent interactions between the test runner and mock providers and real backends.

Core Features & Use Cases

Structured test formats: JSON-based test definitions that specify steps, assertions, and mock/live execution modes.
Deterministic test execution: A single test file drives a sequence of actions, timing, and verifications to validate behavior.
World-wide use cases: Useful for validating control sockets, CLI runtimes, and integration paths in both mock and live environments.

Quick Start

Place your end-to-end test in tests/e2e and run ikigai-ctl commands to execute and verify it.

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 for ikigai workflows?▼

End-to-end tests for ikigai workflows are structured as JSON-based test definitions placed in the tests/e2e directory, specifying execution steps, assertions, and mock or live modes. The index.json file dictates the execution order for these tests.

What is the difference between mock and live modes in e2e testing?▼

Mock and live modes distinguish e2e testing environments: mock mode uses mock providers to simulate behavior, while live mode verifies behavior against real backends through the control socket to ensure consistent interactions.

How do I execute e2e tests using ikigai-ctl?▼

You execute and verify e2e tests by running ikigai-ctl commands after placing your JSON test files in the tests/e2e directory. The test runner drives the sequence of actions, timing, and verifications defined in the test schema.

What is the JSON schema for ikigai e2e test definitions?▼

The JSON schema for e2e tests defines step types, assertions, and execution rules that govern test behavior. This format drives deterministic test execution by validating a sequence of actions and verifications against either mock or live environments.

Does e2e testing verify behavior through the ikigai control socket?▼

Yes, e2e testing verifies ikigai behavior specifically through its control socket. This ensures consistent interactions between the test runner, mock providers, and real backends during both mock and live execution modes.