Run Playwright UI regression sweeps across Breeze MSP workflows and file GitHub issues.
npx skills add https://github.com/LanternOps/breeze --skill ui-qa-sweep
Please help me install this Agent Skill. Skill: ui-qa-sweep Source: https://github.com/LanternOps/breeze/tree/main/.claude/skills/ui-qa-sweep Command: npx skills add https://github.com/LanternOps/breeze --skill ui-qa-sweep
Broad regression QA of the Breeze RMM web UI via Playwright — exercising everyday MSP workflows and setup tasks, logging functional PASS/FAIL plus UI/UX observations, and filing GitHub issues from findings. Use this when you need a skeptical, whole-app sweep to validate regressions after merges or PRs, rather than testing a single feature in isolation.
Run a full browser-based UI regression sweep against the Breeze UI on a reachable test environment.
High-intent search queries and answers about installing and using this skill.
A Playwright UI regression sweep executes browser-based end-to-end flows across MSP workflows like login, navigation, and device actions. It validates the web app for regressions after merges by logging functional PASS/FAIL results and UI/UX observations.
Automated UI regression testing for post-merge validation translates UI-affecting changes into end-to-end browser flows. It exercises typical workflows across the web app to uncover defects and produces a searchable record of failures with reproducible steps.
Documenting QA test failures involves capturing an evidence log with console messages and UI/UX observations during the sweep. This log produces actionable defects with reproducible steps suitable for direct GitHub issue creation.
Yes, the Playwright QA sweep covers remote sessions and patch workflows alongside alerts, scripts, and admin config flows. It applies broad regression coverage across these typical MSP workflows to validate functional stability.
Use a full UI regression sweep when you need a skeptical, whole-app validation after PRs rather than testing a single feature in isolation. It applies end-to-end validation across everyday workflows to catch broad regressions.
Browser-based QA sweeps require a reachable test environment to execute end-to-end flows. They focus on functional PASS/FAIL logging and UI/UX observations, meaning they validate existing workflows rather than generating new unit-level test coverage.
drvossInspect DOM state, network traffic, and Core Web Vitals in Chrome DevTools.
darellchua2Extract commit details and post structured updates to GitHub issues and Jira tickets.
muddyrainCapture, filter, and export Unity console logs during runtime sessions.
divad12Automate browser-based end-to-end UI testing with Playwright MCP and report PASS/FAIL/CONCERN per scenario.
