Web Test Agent — Testing skill for Claude Code

web-test-agent

**Black-box end-to-end web testing, driven from nothing but a URL.**

   

Point it at a deployed site, and hand it the requirement documents you have. It follows a tester's process — analyse the requirements, design the test cases, execute them, analyse the results — and stops after each step for you to review and approve. You end up with requirements traced to test cases, a quality-gate decision you can block a release on, and a bug report ready to import into Jira.

No access to the target's source code is required, and none is assumed.

---

Table of contents

• Why this exists
• How it works
• Quick start
• The four steps
• Approval gates
• The test plan is the contract
• Two execution paths: PW and MCP
• The quality gate
• Artifact layout
• Configuration
• Project structure
• Guardrails
• Troubleshooting

---

Why this exists

Most test automation starts from the inside: you have the repo, the components, the routes. This workflow starts from the outside, the way a user or an auditor does. That makes it useful in the cases where conventional tooling has nothing to grip:

• A deployed site whose source you do not have, or do not want to read.
• A staging environment you need smoke coverage on before a release, today.
• A third-party or legacy app nobody on the team can still explain.
• A regression net around an app while its inter