Web app testing

# Use Web app testing in your agent

## Objective
Use the existing webapp-testing skill only when it directly covers the requested task.

## Prerequisites
- local application URL or static HTML file
- user journey and expected behavior
- server command and port when the application is not already running
- Python
- Playwright synchronous API and Chromium
- optional scripts/with_server.py helper for local server lifecycle

## Permissions
- write and execute scoped Python Playwright scripts
- launch a local browser and read rendered application state
- start and stop explicitly scoped local application servers
- interact with and potentially mutate local test application state

## External effects
- local browser and optional application-server processes are started and stopped
- Python scripts, screenshots, DOM captures, and logs can be written to disk
- browser actions can mutate the local application's test state

## Procedure
- Open the canonical source pinned to revision fa0fa64bdc967915dc8399e803be67759e1e62b8.
- Read the skill instructions before calling its tools.
- Ask for confirmation before any paid, destructive, or remote effect not already authorized.
- Run the procedure within the requested scope and retain useful evidence.

## When not to use
- deploy an application
- test a remote production mutation without authorization
- replace unit tests with screenshots

## Expected result
- native Python Playwright automation script
- observed UI behavior, screenshots, rendered DOM evidence, or browser console logs

## Guardrails
- Show the proposed changes before any external action.
- Do not publish, send, delete, pay for, or change remote state without explicit authorization.
- Preserve unrelated changes and stop if the scope becomes ambiguous.

## Output format
- Outcome or verdict.
- Files or actions involved.
- Checks run and observable evidence.
- Remaining blockers or limitations.

• Requires · Python
• Requires · Playwright synchronous API and Chromium
• Requires · optional scripts/with_server.py helper for local server lifecycle

# Verify the Web app testing outcome

## Objective
Check that the webapp-testing skill was used within scope and that its effects match the authorized request.

## Checks
- Compare the source and revision with the manifest.
- Separate local, browser, and external evidence.
- Report any permission or effect that was not disclosed.

## Guardrails
- Show the proposed changes before any external action.
- Do not publish, send, delete, pay for, or change remote state without explicit authorization.
- Preserve unrelated changes and stop if the scope becomes ambiguous.

## Output format
- Outcome or verdict.
- Files or actions involved.
- Checks run and observable evidence.
- Remaining blockers or limitations.

sha256:f701ccd98bf70fde21cd1638e5feb07fa563e85bef3479eb9a2f83fe518ff2c9

# Verify Web app testing in your agent

## Result to check
Verify the use of webapp-testing for the current bounded task.

## Failure signals
- The source or revision does not match the manifest.
- A permission or external effect was not disclosed.
- The output does not match the expected artifacts.
- The skill activated for a declared non-trigger.

## Checks
- Compare the SHA-256 of SKILL.md with sha256:51b7349e77ec63b7744a6f63647e7566a0b4d2e301121cc10e8c2113af6556a2.
- Confirm the permissions actually used and the observed effects.
- Verify artifacts with the narrowest available test.
- Separate local, browser, and external evidence in the report.

## Expected result
- native Python Playwright automation script
- observed UI behavior, screenshots, rendered DOM evidence, or browser console logs

## Guardrails
- Show the proposed changes before any external action.
- Do not publish, send, delete, pay for, or change remote state without explicit authorization.
- Preserve unrelated changes and stop if the scope becomes ambiguous.

## Output format
- Outcome or verdict.
- Files or actions involved.
- Checks run and observable evidence.
- Remaining blockers or limitations.

• Requires · Python
• Requires · Playwright synchronous API and Chromium
• Requires · optional scripts/with_server.py helper for local server lifecycle

# Make the Web app testing check reusable

## Objective
Turn the successful checks into a bounded checklist for the next use of webapp-testing.

## Checks
- Keep only observable signals.
- Tie each permission to its expected effect.
- Add an explicit stop if the source or revision changes.

## Guardrails
- Show the proposed changes before any external action.
- Do not publish, send, delete, pay for, or change remote state without explicit authorization.
- Preserve unrelated changes and stop if the scope becomes ambiguous.

## Output format
- Outcome or verdict.
- Files or actions involved.
- Checks run and observable evidence.
- Remaining blockers or limitations.

sha256:95ff794874deb1f7a4190401e975ae8a5d83903b3332000f72138593890f0567