9 / 139 · 13 Browser Automation with Playwright · Pre-Requisites: Discover the Application and Produce Customization Artifacts← prev⊞ allnext →☰ Read as one page
1.9Step 3 — If there is no Site Map, traverse the app deliberately
If no Site Map exists, discover structure from navigation and exploratory traversal.
Traverse these areas in order
- landing page
- primary nav
- footer nav
- auth entry points
- post-login landing page
- settings/account/admin menus
- search/browse/detail pages
- transaction flows
- error or empty states that appear during use
Capture as you go
For each page or route, note:
- page name
- route or URL pattern
- purpose
- domain/feature area
- whether it belongs in smoke, regression, or low-priority coverage
- whether it is public, authenticated, or role-restricted
Copy-paste prompt for Claude Code
Explore the running application and infer its real structure.
From navigation, pages, and visible flows, extract:
- top-level pages
- nested pages
- route patterns
- major user journeys
- public vs authenticated areas
- likely role-specific areas
Write structured notes into:
- docs/discovery/navigation-notes.md
- docs/specs/product-under-test.md
Do not scaffold code yet.