Webapp Testing

Run targeted browser checks on a local web app with Python Playwright. Capture the failing interaction and relevant browser evidence so another developer can repeat it.

Reproduce a local UI failure with Playwright

Give the agent an approved local page and one visible expected result. Save a script and evidence another developer can rerun.

Provide the local route, expected behavior and synthetic inputs.

Copy the request into a new Floatboat conversation and provide the required material.

Download Floatboat

Your request for Floatboat

Preview and copy the request. It is not sent automatically from this page.

Reference: Webapp Testing
https://github.com/anthropics/skills/blob/main/skills/webapp-testing/SKILL.md

Read the original documentation and check the current environment and dependencies. Propose any new installation or tool connection before proceeding.

My task:
Use Webapp Testing on my local settings form. Enter synthetic values that should trigger the required-field message, save a Playwright assertion and record the screenshot and browser errors. Use only my approved local start command.

Expected deliverable:
A repeatable script and a short report with actual results.

About Webapp Testing

Anthropic’s Apache-2.0 Webapp Testing Skill directs a coding agent to write native Python Playwright scripts. It supports static HTML and local web apps, and includes a helper to manage approved development servers. A screenshot records visible state while an assertion determines whether the behavior passed.

Webapp Testing Use Cases for Local Browsers

Choose an interaction with a visible expected result. Pair screenshots and console output with a narrow assertion that a teammate can rerun.

Reproduce a form validation issue

Give the agent a local URL, synthetic form values and the error message you expect. It can submit the fixture, capture the actual UI state and retain an assertion for the missing message.

Check a loading transition

Start with a page whose data arrives after initial render. Wait for the relevant state, inspect the rendered DOM and record whether the final control becomes usable.

Collect evidence for a broken route

Use a test session to open the route that fails. Save the navigation sequence, screenshot and relevant console error together so a developer can locate the failure.

Verify an isolated HTML change

Open the approved local HTML fixture and check a keyboard or click interaction. Leave a small script with the exact assertion so the same behavior can be retested later.

How to Reproduce a Local Web App Failure

Start with one observable failure. The agent can use an existing test server or start an approved local command, then capture only the evidence needed to repeat the check.

  1. Set the test boundary

    Give the agent a local URL or HTML file, approved fixtures and one observable success condition. Configure Python Playwright and the required browser.

  2. Exercise the interaction

    Use the running local app or an approved server command with the bundled helper. Wait for the expected state and inspect the DOM before choosing locators.

  3. Hand off reproducible evidence

    Save the script, actual assertion result and any necessary screenshot or console output. Record the command and local route used.

Explore More Agent Skills

Read another Skill guide and check its original source before using it.

Webapp Testing FAQ

Which browser toolkit does it use?
The upstream instructions use native Python Playwright scripts and provide a helper for starting local development servers.
Can it check a static HTML file?
Yes. The source includes an example using a local file URL, so a server is only needed when the app requires one.
Do I have to start a new server?
Reuse the running approved server when one is already available. Use the helper only if you have reviewed the local start command.
Is a screenshot enough to prove a fix?
A screenshot records a rendered state. Keep a repeatable assertion and its output to verify the actual interaction.
Which Claude Code plugin includes it?
Anthropic lists Webapp Testing in its example-skills plugin. The browser and Python dependencies still need to be available.
Can I use production accounts as test data?
Use approved test environments and synthetic fixtures for this workflow. Set aside any check that needs production access until its scope is agreed.