QA testing with Claude Code and Playwright

What Claude Code does for QA testing

• Writes end-to-end tests for the flows that matter: sign-up, checkout, the main screens.
• Runs the suite, reads the failures and fixes the test or the code, saying which.
• Drives a real browser to check a change by hand, and files bugs with steps and screenshots.
• Finds flaky tests and quarantines them with an issue, instead of retrying until they pass.

Claude Code features for QA testing

How to set up Claude Code for QA testing

1. Connect the tools

   Add the Playwright MCP server so Claude Code can open your app in a browser. For a test suite in the repository, install Playwright as you normally would; Claude runs it like any other command.

   # A real browser for exploratory checks
   claude mcp add playwright npx @playwright/mcp@latest
   
   # A test suite, if you don't have one yet
   npm init playwright@latest

2. Write the rules in CLAUDE.md

   Claude Code reads CLAUDE.md at the start of every session, claude -p runs included. Put the job's rules there, or in a skill under .claude/skills/ if they're long. See the CLAUDE.md guide.

   ## QA rules
   - Test against the local or staging app, never production.
   - Use the test accounts in .env.example, never real ones.
   - A failing test is a finding: say whether the test or the code
     is wrong before you change either.
   - Every bug report: steps, expected, actual, a screenshot and
     the commit you tested.
   - Don't delete or skip a test to make the suite pass.

3. Run it without the interactive interface

   claude -p runs one task and exits, so cron, CI or another tool can start it. Choose what it may do without asking with --allowedTools or --permission-mode; --output-format json returns the result with its cost.

   # Run the suite and fix failures, from CI or cron
   claude -p "Run npx playwright test and fix the failures, following CLAUDE.md" \
     --allowedTools "Bash,Read,Edit"

4. Put it on a schedule

   Make it a cloud scheduled task with /schedule (Pro, Max, Ultra, Team and Enterprise), a desktop scheduled task, or /loop while a session stays open. See how to make Claude Code proactive.

Source: Claude Code documentation

Limits and safety

• It tests what it can reach: a local or staging app with test data, not production.
• A passing suite covers only the flows someone wrote tests for. Ask it to list what isn't covered.
• Browser runs are slow and use more of your plan. Run the full suite on a schedule and a smoke test on each change.
• Since Claude Code v2.1.302, claude -p starts in Manual mode: an action that needs approval is denied unless a rule allows it. Allow only the tools the job needs.

Claude Code or Codex for QA testing?

The rules carry over. Write them once in AGENTS.md and put @AGENTS.md in CLAUDE.md, and both agents read the same file.

Step by step for the other agent: QA testing with Codex.

Make QA testing someone's job

Commands run when someone remembers to run them. Crewmark turns your own Claude Code into an AI employee with a role, a goal in numbers, working hours and a heartbeat, so the work happens on schedule and shows up on a board.

1. Start from the role

   The AI software engineer, with these rules in its brief.

2. Put the work on its board

   Add the job as a recurring issue. The employee wakes on its heartbeat, does it and reports in a comment.

3. Related

   GitHub issues covers what happens to the bugs it files.

FAQ