skills.rest
bex-co
bex-coOFFICIAL
Explore all skills by this author →
WebsiteGitHub

qa-find-bugs-dashboard

Tests the Beancount.io dashboard with headless Playwright to reproduce, trace, and report bugs.

275|32|Updated Oct 2, 2020
Search Tags:#qa#web testing#regression#playwright#dashboard testing#bug hunting#headless browser
One-click install
npx skills add https://github.com/bex-co/beancount-io --skill qa-find-bugs-dashboard-bex-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-find-bugs-dashboard
Source: https://github.com/bex-co/beancount-io/tree/main/.agents/skills/qa-find-bugs-dashboard
Command: npx skills add https://github.com/bex-co/beancount-io --skill qa-find-bugs-dashboard-bex-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually hunting for bugs in a live web dashboard is slow and inconsistent, and findings often lack reproduction steps, root-cause traces, or deduplication against existing work. This Skill runs a disciplined QA bug hunt against the Beancount.io dashboard using a headless browser, producing verified, deduplicated findings. ## Core Features & Use Cases - Headless browser QA: Drives Playwright MCP with an isolated QA profile so the user's windows, cursor, and clipboard stay undisturbed, authenticating with QA_EMAIL and QA_PASSWORD from dashboard/.env. - Journey-based coverage: Sweeps twelve defined journeys (auth, discovery, overview, journal, accounts, reports, export, files, query, import, settings, accessibility) with concrete observable promises for each. - Reproduce, trace, dedupe, report: Reproduces each candidate from a fresh page load, traces root causes to the owning source package, deduplicates against open and completed work, and files findings through pm. - Use Case: Run the skill against production with w4 SHIP=1 DRY_RUN=1 to audit the dashboard before a milestone, capturing sanitized evidence without writing to the board or pushing code. ## Quick Start Ask the agent to run a dashboard QA bug hunt against production using the credentials in dashboard/.env and report any reproduced bugs.

Frequently Asked Questions about qa-find-bugs-dashboard

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

FAQPage Schema
How do I run automated QA on a web dashboard with Playwright?▼

Launch Playwright MCP with --headless --isolated, authenticate using the credential helper with QA_EMAIL and QA_PASSWORD from dashboard/.env, then sweep the defined journeys such as auth, journal, and reports. Reproduce each failure from a fresh page load before retaining it as a finding.

How do I test a web app in the background without disturbing my browser?▼

Use a headless browser with an isolated QA profile rather than attaching to your regular browser. Verify the active MCP launch configuration first, since a running headed session ignores later config edits, and use page/context APIs instead of OS mouse or keyboard input.

Can headless Playwright test file uploads and print dialogs?▼

File uploads work through file-input and file-chooser APIs with authorized fixtures, and print can be checked via print media or a headless PDF. Native file dialogs, the native print dialog, and real screen readers cannot be verified headlessly and are recorded as unverified.

Why does a GraphQL request returning 200 still indicate a bug?▼

HTTP 200 only confirms the request completed; GraphQL can return errors or empty data in the response body. Inspect the sanitized response payload and the rendered UI state rather than treating the status code as success.

What are the limitations of headless browser QA?▼

Headless sessions cannot verify native dialogs, actual screen-reader behavior, or OS-level interactions, and results against synthetic local fixtures must be labeled as simulations. Visible-browser checks run only when explicitly requested.

Related Skills

Explore More Software Engineering Skills→
dynatrace-ossdynatrace-oss
10

snowflake-synthetic

Provisions and maintains synthetic test data environments in Snowflake for DSOA telemetry dashboards.

Official
Advanced
seasonedccseasonedcc
4

testing

Find and run Vitest-based unit tests in TypeScript projects.

Official
Intermediate
BitSleuthAIBitSleuthAI
1

webapp-testing

Test and debug Expo React Native apps on iOS and Android.

Official
Advanced
eric-sabeeric-sabe
1

web-design-reviewer

Inspect web applications across viewports and apply source-level fixes for design and accessibility issues.

Community
Intermediate