playwright-testing
by kjaylee
Web & Frontend DevelopmentBrief
Test web applications and games using Playwright on MiniPC.
Description
What This Skill Does
Runs Playwright browser automation on a MiniPC node using headless Chromium. Handles web app and game QA, screenshot capture, DOM inspection, and console log collection. Executes via nodes.run or browser.proxy rather than the local machine.
Running tests on a dedicated MiniPC node keeps browser execution off the development machine and avoids display dependency issues.
When to Use It
- Verifying a game loads and renders its canvas correctly
- Capturing screenshots of a web app at specific states
- Checking for JavaScript console errors during page interaction
- Automating click sequences to test UI flows
- Confirming score or state changes after user input
Example Workflow
User asks: test that the game at localhost:9877 loads and the canvas is visible
- 1
Navigate to http://localhost:9877/game.html on MiniPC via browser.proxy or nodes.run
- 2
Wait for networkidle state to ensure JS has finished executing
- 3
Locate the canvas element and assert it is visible
- 4
Click the canvas to trigger game interaction
- 5
Take a screenshot and capture any console errors
Screenshot saved to /tmp/game-test.png confirming canvas renders; console error list returned
Installation
clawhub install kjaylee/playwright-testingRun the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.