Understand your service with a map of its pages
Find pages and connections, inspect individual results, and see where to verify next.
Turn a page list into a structure
When taking over a service or adding features quickly, it is easy to lose track of its screens and connections. The service map visualizes what it discovers in the running service.
The current app calls this feature Sitemap. Choose a starting URL and collection scope in your project. Authenticated areas need working access to the target service.
Move from the map to evidence
Open a page to inspect its overview, SEO and quality checks, linked tests, and connections. Use the collected information to choose important areas for further checks.
Create a scenario draft from a page, then add executable assertions. For checkout, verify that an order is saved after completion rather than merely checking that the button exists.
Compare like with like
Compare collections to inspect added or missing pages and visual changes. Keep the starting URL, authentication, and scope comparable so collection differences are not mistaken for product changes.
The map shows discovered structure. Unlinked screens and input-dependent states may remain unobserved. Use the map as a starting point for tests of real user goals.
