e2e-test

End-to-End Test Generation

Generate comprehensive end-to-end tests for: $ARGUMENTS

Parse $ARGUMENTS for:

• A specific flow name (e.g., auth, payment, crud, search, settings, admin, profile, responsive)
• --all flag: generate E2E tests for every discovered user flow
• --visual flag: include visual regression testing with baseline screenshots
• If no arguments provided, default to --all

---

Step 1: Analyze Application Flows

1.1 Detect Project Type and Structure

# Detect if this is a web project (Next.js / React)
ls -la package.json 2>/dev/null
ls -la next.config.* 2>/dev/null
ls -la app/ 2>/dev/null
ls -la src/app/ 2>/dev/null
ls -la pages/ 2>/dev/null

# Detect if this is a mobile project (React Native / Expo)
ls -la app.json 2>/dev/null
ls -la expo-env.d.ts 2>/dev/null
ls -la metro.config.* 2>/dev/null
ls -la android/ 2>/dev/null
ls -la ios/ 2>/dev/null

1.2 Scan Web Routes (Next.js App Router)

Use Glob to find all route files:

• **/app/**/page.tsx — Next.js 13+ App Router pages
• **/app/**/page.jsx — JSX variant
• **/pages/**/*.tsx — Pages Router (legacy)
• **/pages/**/*.jsx — JSX variant

For each discovered page file:

1. Read the file to understand the component
2. Extract the route path from the file system path (e.g., app/dashboard/settings/page.tsx maps to /dashboard/settings)
3. Identify dynamic route segments (e.g., [id], [slug], [...catchAll])
4. Detect route groups (group-name) and exclude them from the URL path
5. Identify layout files (layout.tsx) that wrap multiple routes
6. Detect loading states (loading.tsx) and error boundaries (error.tsx)
7. Detect middleware files (middleware.ts) that may redirect or protect routes
8. Identify parallel routes and intercepting routes if present

1.3 Scan React Native Screens (if mobile project exists)

Use Glob to find all screen files:

• **/screens/**/*.tsx
• **/screens/**/*.jsx
• **/app/**/_layout.tsx (Expo Router)
• **/app/**/index.tsx (Expo Router)