nexu-e2e-test

Verify end-to-end integration between Nexu and the OpenClaw gateway across restarts.

3.2k|259|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/nexu-io/nexu --skill nexu-e2e-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nexu-e2e-test
Source: https://github.com/nexu-io/nexu/tree/main/skills/localdev/nexu-e2e-test
Command: npx skills add https://github.com/nexu-io/nexu --skill nexu-e2e-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies end-to-end integration between Nexu and the OpenClaw gateway, ensuring skill loading and session handling after restarts.

Core Features & Use Cases

  • End-to-end testing of gateway-to-Nexu skill loading
  • Validation of session-store interactions and auto-reply pipeline during restarts
  • Smoke tests to confirm embedded agent path routing and skill availability in local setups.

Quick Start

Run the Vitest-based tests inside the OpenClaw worktree to verify skill loading after gateway restart.

Frequently Asked Questions about nexu-e2e-test

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

FAQPage Schema
How do I test gateway skill loading and session preservation after a restart?

To test gateway skill loading and session preservation after a restart, you run Vitest-based tests inside a local OpenClaw worktree to verify the embedded agent path and session-store logic.

What is the best way to validate session-store interactions during CI gateway restarts?

Validating session-store interactions during CI gateway restarts involves executing end-to-end tests that exercise the auto-reply pipeline across multiple restarts using a running gateway configured for testing.

Do I need a running OpenClaw gateway to test the auto-reply pipeline?

Yes, you need a running OpenClaw gateway configured for testing, along with a local OpenClaw worktree containing Vitest tests and a test workspace to exercise the auto-reply pipeline.

How does mocking chokidar help with end-to-end gateway testing?

Mocking chokidar helps end-to-end gateway testing by simulating file watching events, allowing the Vitest tests to safely verify skill loading and availability without relying on real filesystem changes.

Can I use Vitest to smoke test the embedded agent path routing in local development?

Yes, you can use Vitest to run smoke tests that confirm embedded agent path routing and skill availability in local development setups before deploying changes to the gateway.