Goal
Verify that a customer can orient themselves, navigate or search for a representative need, understand results, and reach a relevant product decision state.
Preconditions
- A representative query, category, or customer need is defined from the storefront or repository.
- Empty and no-result inputs do not expose personal or prohibited content.
Collection route
- Begin at the home page or a material landing page.
- Use primary navigation and, when available, storefront search.
- Exercise loading, suggestion, result, filter/sort, empty, no-result, and recovery states that can be reached safely.
- Verify result counts, visible products, availability cues, prices, imagery, links, URL/history, and keyboard behavior.
- Open a relevant product and verify that the discovery context leads to a coherent product decision.
Evidence to reuse
- Route/query, result count, filters, sort, market, viewport, and URL/history state;
- screenshots of populated, empty/no-result, overlay, and product-handoff states;
- accessible names, focus behavior, console/page errors, failed requests, and slow or stale responses;
Return evidence
Attach observations to the selected Check IDs that required them. These steps are an evidence-collection route, not an additional Check or independent Pass/Fail result. Execute only steps needed by selected Checks, preserve their specific criteria, and use the check evaluation workflow for terminal outcomes. The operating contract owns permissions and the checkout stop boundary.