Playwright App Testing
Testing & Qualityplaywright-app-testingPlaywright App Testing is an Agent Skill for testing & quality published in the Expensify/App repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Test the Expensify App using Playwright browser automation. Use when user requests browser testing, after making frontend changes, or when debugging UI issues
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/Expensify/App/blob/HEAD/.claude/skills/playwright-app-testing/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/playwright-app-testing, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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:
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
- Verify server: Check Rspack process is running
- Navigate: Open
https://dev.new.expensify.com:8082/in the browser - 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: Magic code: Always
000000
- Onboarding: The
SKIP_ONBOARDINGenv flag is set tofalseby default in.env. Whenfalse, onboarding screens will appear after sign-in for new accounts. Unless you are specifically asked to test onboarding, update the flag totruebefore starting the dev server so that onboarding is bypassed entirely:
If you need to test onboarding flows, set it back tosed -i '' 's/SKIP_ONBOARDING=false/SKIP_ONBOARDING=true/' .envfalse:
You can check the current value with:sed -i '' 's/SKIP_ONBOARDING=true/SKIP_ONBOARDING=false/' .env
Important: After changinggrep SKIP_ONBOARDING .envSKIP_ONBOARDINGin.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)