E2E Automation Engineer for Openclaw

An automated testing skill designed to validate end-to-end user journeys using Playwright and browser-based flow verification.

aiweline
v1.1.0
May 8, 2026
0
784
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install e2e-flow-test

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install e2e-flow-test using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is E2E Automation Engineer?

The E2E Automation Engineer is a specialized capability for AI agents designed to validate real user journeys through sophisticated browser automation. This skill within the Openclaw Skills ecosystem focuses on full-path behavior, ensuring that multi-page interactions and integration points work correctly in a way that unit tests cannot verify. By simulating actual user behavior, it provides a robust safety net for complex applications.

This skill leverages Playwright to execute automated flows, allowing agents to verify that changes across multiple controllers, pages, or services do not break the end-to-end experience. It is built to handle the complexities of modern web applications, providing actionable evidence whenever a user flow diverges from the expected path, thus maintaining the integrity of the entire software lifecycle.

E2E Automation Engineer Use Cases

  • Executing Playwright browser flow testing for multi-step UI paths.
  • Performing end-to-end regression checks after significant code changes.
  • Validating integration correctness across multiple services and frontend controllers.
  • Verifying business-critical acceptance paths and user journeys in a real browser environment.

How E2E Automation Engineer Works

  1. Identify the specific business flow or user journey that requires end-to-end validation.
  2. Select the narrowest possible test specification, case ID, or grep target to ensure efficient execution.
  3. Prepare the necessary isolated runtime environment or route state before initiating the browser check.
  4. Execute the standardized E2E command within the supported framework to start the automation.
  5. Inspect the failure points at the exact user-flow step where the behavior diverged from requirements.
  6. Re-run the smallest scope of the test after applying fixes to confirm the solution.
  7. Generate a comprehensive report detailing the executed scenario, results, and any remaining gaps.

E2E Automation Engineer Setup

To deploy this capability within your Openclaw Skills environment, ensure your repository is configured for Playwright. Use the following commands to initiate the E2E runner:

# Run the standard repository-supported browser tests
php bin/w e2e:run

# Run a specific test scope using a grep filter
php bin/w e2e:run --grep "checkout-flow"

Note: Avoid using the default port 9501 for AI-driven testing if the flow requires a dedicated instance. Always ensure that dedicated instances are stopped after runtime-sensitive validations are complete.

E2E Automation Engineer Data Schema & Taxonomy

The E2E Automation Engineer skill organizes its testing lifecycle and results using the following schema to ensure compatibility with Openclaw Skills standards:

Category Description
Inputs User flows, module targets, login credentials, and seed data prerequisites.
Configuration Preferred spec files, module filters, and specific grep scopes for targeted execution.
Execution Logs Real-time browser path evidence, pass/fail status, and divergence step analysis.
Cleanup State Metadata for managing and terminating dedicated runtime instances and ports.

E2E Automation Engineer Advanced Features

  • Support for route-backed execution and multi-step UI path validation.
  • Granular execution control via grep targets and case ID filtering to reduce testing overhead.
  • Automated cleanup of dedicated WLS runtime instances after high-risk validation tasks.
  • Integration with the Openclaw Skills collaborative roster for cross-agent issue notification.
  • Reporting of flaky prerequisites and environmental risks to ensure transparent testing results.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*