swayzio-admin-e2e

Smoke-tests the live Swayzio Admin Dashboard via Browser Use cloud browser and Clerk email-code sign-in.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/mylesfranklin/swayzio-admin-dashboard --skill swayzio-admin-e2e-mylesfranklin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swayzio-admin-e2e
Source: https://github.com/mylesfranklin/swayzio-admin-dashboard/tree/main/.agents/skills/swayzio-admin-e2e
Command: npx skills add https://github.com/mylesfranklin/swayzio-admin-dashboard --skill swayzio-admin-e2e-mylesfranklin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying that a founders-only production admin dashboard actually works end-to-end — sign-in, page loads, and live data APIs — normally requires a real founder's Google account and manual clicking. This Skill provides a persistent QA founder identity and a repeatable harness to smoke-test admin.swayzio.com against real Stripe, HubSpot, and app-database data. ## Core Features & Use Cases - Founder sign-in automation: Drives a Browser Use cloud browser with a persistent profile, pulling Clerk email verification codes from an AgentMail inbox so the QA identity (role=founder) passes the founders-only gate. - Live API assertions: Calls the dashboard's own data endpoints (/api/hubspot/metrics, /api/stripe/metrics) with the live Clerk session token to confirm real metrics like totalContacts, mrr, and payingSubscriptions are returned. - Auth-gate verification: Confirms unauthenticated requests to data APIs return 401/403/404, proving the founders-only boundary holds. - Use Case: After deploying a change to the admin dashboard, run the standard smoke run to confirm the Stripe and HubSpot analytics pages render KPIs and the APIs return real data before founders rely on them. ## Quick Start Run an end-to-end smoke test of admin.swayzio.com: sign in as the QA founder, load the Stripe and HubSpot analytics pages, and verify the data APIs return real metrics.

Frequently Asked Questions about swayzio-admin-e2e

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

FAQPage Schema
How do I run an end-to-end smoke test of the Swayzio admin dashboard?

Source .e2e/env, then run browser-use cloud connect and open https://admin.swayzio.com. Confirm the dashboard loads, open the Stripe and HubSpot analytics pages, assert the data APIs return real metrics, and verify unauthenticated requests are rejected.

How do I sign in to a Clerk-gated app with email verification codes in a browser test?

Use the Browser Use connected-session model (cloud connect plus open/state/click/input) so all steps share one persistent browser. Pull the 6-digit Clerk code from the AgentMail inbox with the admin_e2e.py inbox-codes helper and enter it in the same session.

Why does the Browser Use cloud v2 tasks API fail for multi-step sign-in flows?

Each v2 task stops its browser session on completion, so you cannot read an email code and re-enter it on the same session. Use the connected-session model instead, which keeps one persistent browser across all steps.

How do I verify a founders-only API gate actually blocks unauthorized requests?

From the signed-in browser, fetch the data endpoint without an Authorization header using browser-use eval and check the status code. It must return 401, 403, or 404 — never 200 with data.

Can this harness modify production data in the admin dashboard?

No. The QA account is read-only and the admin dashboard exposes only analytics reads with no destructive writes. Verification reads against production are safe by design.