Service map
See discovered pages and connections, then inspect results for each page
The service map visualizes pages and connections discovered in the running service. Scan the structure, then open a page's collected information and check results to identify what has been observed and what needs verification.
Service map has Screens, Features, and User flows views. Screens contain collected observations; features and flows are separately authored or reviewed records linked to expected behavior.
Collect pages
- Select the project and target environment, then open Service map → Screens (서비스맵 → 화면).
- Review the starting URL and scope in collection settings. Collection policies such as robots handling, request delay, and capture reuse belong to the individual collection.
- Start collection and use its log to inspect progress and access failures.
- Inspect discovered pages and connections, then open details for important pages.
Authenticated areas require working access to the target service. Screens without reachable links, or states that depend on particular accounts or inputs, may not be discovered.
Inspect a page
| Detail tab | Content |
|---|---|
| Overview | Page information and captured screen |
| SEO | SEO checks on the collected page |
| Quality | DOM-based checks and collected browser metrics |
| Tests | Tests linked to the page |
| Connections | Links between pages |
Page checks evaluate collected evidence. DOM checks alone do not establish WCAG compliance or prove that checkout and authorization work. Configure dedicated tests for deeper accessibility, performance, or functional checks.
Connect a page to a test
The scenario draft action in page details starts a test definition. Add the intended behavior and executable assertions before running it. Saving a draft does not complete verification.
Page-to-test linking uses metadata.sourceUrl and metadata.pageUrls in test-case.json. Drafts created from a page populate the relevant information. Manually written tests can provide matching URLs to establish the link.
Review changes
In Changes → Structure / Screens, select a baseline and a comparison run. Compare collections to inspect added or removed pages, discovered issues, and captured visual differences. Use comparable starting URLs, authentication, and collection scope. A page missing because login expired or the scope changed is not necessarily a removed product page.
A visual difference is evidence of change. Use the product's intended behavior to decide whether it is an expected design update or a defect.
Continue with behavior checks
The service map shows observed structure. Discovering an important page does not prove that a user can complete a goal. Use Managing UX checks to organize verification by user flow, feature, and persona.