Run any Skill in Manus with one click

$pwd:

playwright-app-testing

Name: Playwright App Testing
Author: Expensify

// Test the Expensify App using Playwright browser automation. Use when user requests browser testing, after making frontend changes, or when debugging UI issues

Run Skill in Manus

$ git log --oneline --stat

stars:4,885

forks:3,851

updated:March 2, 2026 at 15:02

SKILL.md

readonly

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:

ps aux | grep "webpack" | 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 webpack 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_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:
```
sed -i '' 's/SKIP_ONBOARDING=false/SKIP_ONBOARDING=true/' .env
```
If you need to test onboarding flows, set it back to false:
```
sed -i '' 's/SKIP_ONBOARDING=true/SKIP_ONBOARDING=false/' .env
```
You can check the current value with:
```
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)

related-skills.json

same repository

coding-standards.md

from "Expensify/App"

Provides coding standards for React Native — performance patterns, consistency rules, and clean React architecture. Use when writing, modifying, or reviewing code.

2026-05-184.9k

agent-device-evidence.md

from "Expensify/App"

Records iOS/Android native MP4 evidence for test/repro flows extracted from an Expensify GitHub PR or issue. Use when the user asks to "record the flow for PR

2026-05-114.9k

measure-telemetry-span.md

from "Expensify/App"

Use when measuring a Sentry performance span locally with an agent-device replay flow on iOS simulator or Android emulator.

2026-05-064.9k

agent-device.md

from "Expensify/App"

Drive iOS and Android devices for the Expensify App - testing, debugging, performance profiling, bug reproduction, and feature verification. Use when the developer needs to interact with the mobile app on a device.

2026-05-054.9k

sentry.md

from "Expensify/App"

Analyze Sentry issues, spans, crashes, and performance metrics. Use when user requests check in Sentry, asks about performance metrics and spans or asks about crash rates.

2026-03-264.9k

onyx.md

from "Expensify/App"

Onyx state management patterns — useOnyx hook, action files, optimistic updates, collections, and offline-first architecture. Use when working with Onyx connections, writing action files, debugging state, or implementing API calls with optimistic data.

2026-02-224.9k

package.json

"author": "Expensify"

"repository": "Expensify/App"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations15-1253L4

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:

ps aux | grep "webpack" | 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 webpack 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_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:
```
sed -i '' 's/SKIP_ONBOARDING=false/SKIP_ONBOARDING=true/' .env
```
If you need to test onboarding flows, set it back to false:
```
sed -i '' 's/SKIP_ONBOARDING=true/SKIP_ONBOARDING=false/' .env
```
You can check the current value with:
```
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)

playwright-app-testing

Playwright App Testing

When to Use This Skill

Prerequisites Check

Dev Server Details

Playwright Testing Workflow

Dev Environment Sign-In

Example Usage

When NOT to Use This Skill

More from this repository

More from this repository

Playwright App Testing

When to Use This Skill

Prerequisites Check

Dev Server Details

Playwright Testing Workflow

Dev Environment Sign-In

Example Usage

When NOT to Use This Skill