ui_e2e

Automate Playwright-based Chromium browser testing for JiuwenSwarm Todo and Cron UI flows.

2.5k|422|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/openJiuwen-ai/jiuwenswarm --skill ui-e2e-openjiuwen-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui_e2e
Source: https://github.com/openJiuwen-ai/jiuwenswarm/tree/main/tests/ui_e2e
Command: npx skills add https://github.com/openJiuwen-ai/jiuwenswarm --skill ui-e2e-openjiuwen-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, websockets, npm.

What problem does it solve?

Validates JiuwenSwarm’s Web UI flows end-to-end and captures screenshots and logs so browser-interaction bugs and UI regressions can be quickly reproduced and diagnosed.

Core Features & Use Cases

  • Todo Web UI flow verification: Confirms todo creation and status transitions through the chat-driven UI path and checks the Tool Panel rendering.
  • Cron Web UI flow verification: Confirms cron panel behaviors including structured reminders, preview rendering, run-now execution, toggle on/off, and deletion.
  • Evidence-first reporting: Produces report.md and report.json plus backend.log/ui.log and screenshots for each scenario, enabling actionable failure analysis.
  • Runtime interpreter selection: Ensures JiuwenSwarm backend and the web UI are launched from the same chosen Python runtime to reduce environment drift.

Quick Start

Run the full UI e2e suite once and generate artifacts for inspection by executing: python3 -m tests.ui_e2e.run_suite --build.

Frequently Asked Questions about ui_e2e

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

FAQPage Schema
How do I run end-to-end smoke tests for web UI flows using Playwright?

Run end-to-end smoke tests by using Playwright to drive Chromium automation, launching the backend and web frontend with a selected Python runtime to validate expected UI states and tool execution results.

How does UI regression testing capture screenshots and backend logs for failure analysis?

UI regression testing captures evidence by executing browser interactions and writing screenshots, backend logs, and structured report outputs into a designated artifacts directory for actionable failure analysis.

Do I need npm and websockets installed to automate browser testing for web UI panels?

Yes, you need npm and websockets installed alongside Playwright to automate browser testing, as these dependencies drive the Chromium automation and validate the UI panel interactions.

Can I verify cron panel behaviors like run-now execution and toggle on/off through e2e testing?

Yes, e2e testing verifies cron panel behaviors including structured reminders, preview rendering, run-now execution, toggle on/off, and deletion through automated browser interactions.

What is the best way to ensure a clean slate before running web UI smoke tests?

Ensure a clean slate for web UI smoke tests by deleting test jobs by prefix before execution, which prevents previous test data from interfering with deterministic validation.

How do I generate report.md and report.json artifacts after validating todo and cron web UI flows?

Generate report.md and report.json artifacts by executing the UI e2e suite with the build flag, which validates todo and cron flows and writes structured outputs to the artifacts directory.