playwright-testing

What This Skill Does

The playwright-testing skill provides a robust framework for automating web and game testing directly on MiniPC environments within the OpenClaw ecosystem. By leveraging the Chromium headless browser, it allows AI agents to interact with web applications programmatically. This skill is engineered to support the full testing lifecycle, including page navigation, DOM inspection, element interaction (clicking, typing), and visual validation through screenshots. It is optimized for the 'Reconnaissance-Then-Action' pattern, ensuring that agents first assess the state of a web page—ensuring network idle states—before executing complex test sequences. This makes it an essential tool for verifying frontend UI integrity and performing automated game QA without the need for a physical monitor or local GUI.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/kjaylee/playwright-testing Ensure that your MiniPC node is correctly configured and reachable via your OpenClaw network settings, as this skill relies on headless browser execution on remote edge hardware.

Use Cases

• Automated Game QA: Perform repeatable interaction tests on web-based games, such as clicking canvas elements and validating score updates in the DOM.
• UI Regression Testing: Capture full-page screenshots to compare visual layouts across different application states or deployments.
• Dynamic Web App Verification: Debug client-side behaviors by capturing console logs and monitoring network activity during user flows.
• Headless Functional Testing: Validate button availability, form submissions, and data rendering for internal dashboards and static sites.

Example Prompts

1. "MiniPC, please navigate to the local game URL at port 9877, wait for the page to load, click the 'Start' button, and capture a screenshot of the resulting screen."
2. "Run the Playwright test suite located in /home/scripts/smoke_test.py on the MiniPC and report back any console errors caught during the process."
3. "Verify if the 'Submit' button is visible on the web application running at localhost:8080 by performing a DOM inspection via Playwright."

Tips & Limitations

• Always wait for networkidle: Never skip page.wait_for_load_state('networkidle'). Dynamic web apps require the JavaScript environment to stabilize before DOM elements become reliably accessible.
• Headless Requirements: Since MiniPC lacks a physical display, always ensure your Playwright scripts are configured with headless=True to prevent execution errors.
• Security Context: This skill involves executing arbitrary scripts on MiniPC nodes; ensure that only authorized scripts are run to prevent unauthorized file system access.
• Performance: For heavy testing suites, monitor resource usage on your MiniPC, as headless Chromium instances can consume significant CPU and memory if multiple tests run concurrently.