Skip to main content
skill CX Codex

playwright-app-testing — Claude Code skill

playwright-app-testing — a skill for browser automation with Playwright. Runs UI tests after frontend changes, verifies interface behavior, and catches bugs in layout and logic.

MIT ★ 5,104 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Expensify/App --skill playwright-app-testing -a claude-code
Open on GitHub

What playwright-app-testing does

Available for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode. The skill checks whether the dev server is running on https://dev.new.expensify.com:8082/, navigates the app, and interacts with elements through Playwright MCP.

Before using it, confirm Rspack is running (ps aux | grep "rspack"). If the server is not active, start it with cd App && npm run web. When signing into the dev environment, generate an email like user+throwaway<random_digits>@gmail.com and use security code 000000 for existing accounts. The onboarding screen is controlled by the SKIP_ONBOARDING flag in .env. Set it to true to bypass onboarding, or false to test onboarding flows; restart the server after any change.

The skill does not insert arbitrary waits. After each action, it takes a screenshot and only pauses if the page needs time to update. Use it to verify UI changes, debug visual issues, or reproduce bugs in the browser.

What it helps with

  • verify sign-in flow in the dev environment
  • confirm UI changes render correctly after code edits
  • catch visual and interaction bugs in the interface
  • walk through an app scenario manually in the browser
  • debug issues with clicks, text input, or navigation

Example prompts for the agent

  • Test the sign-in flow and create a new expense
  • Check that the expense form validation works after my updates
  • Reproduce the bug: click the submit button and see what happens

How to install playwright-app-testing

1Skills CLI (Vercel)

npx skills add Expensify/App --skill playwright-app-testing -a claude-code

2Manually: put the files in place

~/.claude/skills/playwright-app-testing/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/playwright-app-testing/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about playwright-app-testing

How do I install playwright-app-testing in Claude Code?

Run npx skills add Expensify/App --skill playwright-app-testing -a claude-code, then check ~/.claude/skills/playwright-app-testing/SKILL.md.

What does playwright-app-testing do?

The skill enables browser-based UI testing of the Expensify App through Playwright. It verifies the dev server is running, navigates the app, interacts with UI elements, and captures screenshots for debugging.

What do I need before using this skill?

You need a running dev server (npm run web in the App directory) and Playwright MCP. Sign in with an email like [email protected] and code 000000. To skip onboarding, set SKIP_ONBOARDING=true in .env and restart the server.

Source text

SKILL.md · MIT
---
name: playwright-app-testing
description: Test the Expensify App using Playwright browser automation. Use when user requests browser testing, after making frontend changes, or when debugging UI issues
alwaysApply: false
---

# Playwright App Testing

## When to Use This Skill

Use Playwright testing when:
- User requests testing the App in a browser
- Verifying fixes or improvements you've made to UI/frontend code
- Debugging UI issues

**Proactively use after making frontend changes** to verify your work functions correctly.

## Prerequisites Check

Before using Playwright tools, verify the dev server is running:
```bash
ps aux | grep "rspack" | grep -v grep
```

**If server not running**: Inform user to start with `cd App && npm run web`

## Dev Server Details
- **URL**: `https://dev.new.expensify.com:8082/`

## Playwright Testing Workflow

1. **Verify server**: Check Rspack process is running
2. **Navigate**: Open `https://dev.new.expensify.com:8082/` in the browser
3. **Interact**: Use Playwright MCP tools to inspect, click, type, and navigate

Do NOT add arbitrary waits after actions. Instead, take a snapshot to check the result and only add short waits if the page hasn't updated yet.

## Dev Environment Sign-In

When signing in to dev environment:
- **Email**: Generate random Gmail address (e.g., `user+throwaway<random>@gmail.com`)
    - **New Account**: Press join to create account
    - **Existing Account**: Security code: Always `000000`
- **Onboarding**: The `SKIP_ONBOARDING` env flag is set to `false` by default in `.env`. When `false`, onboarding screens will appear after sign-in for new accounts. Unless you are specifically asked to test onboarding, update the flag to `true` before starting the dev server so that onboarding is bypassed entirely:
    ```bash
    sed -i '' 's/SKIP_ONBOARDING=false/SKIP_ONBOARDING=true/' .env
    ```
    If you need to test onboarding flows, set it back to `false`:
    ```bash
    sed -i '' 's/SKIP_ONBOARDING=true/SKIP_ONBOARDING=false/' .env
    ```
    You can check the current value with:
    ```bash
    grep SKIP_ONBOARDING .env
    ```
    **Important**: After changing `SKIP_ONBOARDING` in `.env`, the web dev server must be restarted for the change to take effect.

## Example Usage

```
Scenario 1: User requests testing
User: "Test sign in to app"
→ Use this skill to verify server and test sign-in flow

Scenario 2: After making UI changes
You: "I've updated the expense form validation"
→ Proactively use this skill to verify the changes work in browser

Scenario 3: Investigating bug
User: "The submit button doesn't work on this page"
→ Use this skill to reproduce and verify the issue
```

## When NOT to Use This Skill

Skip Playwright for:
- Backend service testing
- Unit tests
- Type checking
- Mobile native app testing (requires emulators/simulators)

© Expensify · MIT · Expensify/App

Similar skills

All skills for Testing and QA →

Project sponsors

Companies that keep this analytics open