smoke-test-operator-dashboard

Smoke test Guardian operator dashboard auth and account APIs via browser automation.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/hduoc2003/leviathan-guardian --skill smoke-test-operator-dashboard-hduoc2003
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smoke-test-operator-dashboard
Source: https://github.com/hduoc2003/leviathan-guardian/tree/main/.agents/skills/smoke-test-operator-dashboard
Command: npx skills add https://github.com/hduoc2003/leviathan-guardian --skill smoke-test-operator-dashboard-hduoc2003

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright-core, and includes scripts (resource) components.

What problem does it solve? Verifying that Guardian operator authentication, session login, and dashboard account APIs work end-to-end requires manually coordinating a server, a browser UI, and a local Falcon signer, which is error-prone and slow to repeat. ## Core Features & Use Cases - Guided Manual Smoke Flow: Step-by-step instructions for starting Guardian with operator public keys, launching the operator-smoke-web UI, logging in, listing accounts, and logging out. - Automated Browser Run: A Playwright-based script drives the local signer UI, performs challenge login, exercises account, delta, proposal, and pagination endpoints, and verifies logout invalidates the session. - Flexible Targets: Supports local workspace, remote deployed Guardian, and published npm operator client package configurations. - Use Case: After changing dashboard API code in the Guardian server, run the automated smoke script against a local server to confirm login, account listing, pagination, and logout all behave correctly before merging. ## Quick Start Ask the agent to run the operator dashboard smoke test against a local Guardian server using the bundled automation script.

Frequently Asked Questions about smoke-test-operator-dashboard

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

FAQPage Schema
How do I smoke test the Guardian operator dashboard?▼

Start guardian-server with GUARDIAN_OPERATOR_PUBLIC_KEYS_FILE pointing to a writable JSON file, launch the operator-smoke-web UI on port 3003, then either follow the manual flow or run the bundled run-operator-smoke.mjs script for an automated browser pass.

How do I run the automated operator smoke test with Playwright?▼

Install playwright-core into a scratch directory, start Guardian and the smoke UI, then run node .agents/skills/smoke-test-operator-dashboard/scripts/run-operator-smoke.mjs with GUARDIAN_URL, GUARDIAN_OPERATOR_SMOKE_URL, and the public keys file environment variables set.

Can I smoke test a remote deployed Guardian server?▼

Yes, keep the same local operator-smoke-web UI and change only the VITE_GUARDIAN_TARGET environment variable to the deployed Guardian HTTP endpoint. The same login, account listing, and logout assertions apply.

Why does operator login fail with invalid credentials?▼

The server must be started with GUARDIAN_OPERATOR_PUBLIC_KEYS_FILE pointing at the JSON file updated from the UI's generated signer. Compare the UI commitment with the commitment derived by the server to confirm they match.

Why do I get 401 on account routes after login?▼

Check that requests are proxied same-origin through /guardian and that fetch calls use credentials: include so the session cookie is sent. Also note that a server restart clears in-memory sessions, requiring a fresh login.