Managing UX checks

Different views of the same service call for different checks. Combine scenarios, the feature catalog, and personas to decide which parts of the user experience to verify.

These are ways to organize coverage. Selecting a perspective does not automatically evaluate the entire UX.

By user flow

Open Service map → User flows to add an ordered flow. Each step stores a page URL, user action, and expected outcome. Link relevant features and tests, and edit the step order as needed.

Sources are Observed / AI proposal / Manual. Observed flows require evidence; user confirmation is tracked separately. Saving or confirming a flow does not run tests. The AI test-writing action requests a draft from its steps.

Define a scenario around a user goal. Assert that the goal was completed, rather than only checking that pages opened.

For a booking flow, select a date and options, confirm the booking, and check that the booking record contains the chosen values. An open confirmation page alone is not sufficient evidence.

Use tags, filters, and saved views in test management to group related tests. A saved view stores selection conditions; its contents can change when tests or tags change.

By feature

Use Service map → Features to describe capabilities the product should provide and link their scenarios.

1. Add a feature with a name, area, description, and owner.
2. Link scenarios that verify it. Use scenario synchronization to organize existing definitions.
3. Review healthy, issue, or needs-review status alongside execution evidence.
4. If you request AI suggestions for missing features, review the suggestions and select the relevant items.

Tracking booking creation, changes, and cancellation separately avoids treating one successful booking test as proof that all booking functions work. Adding a catalog entry does not run a test.

By persona

Compare a flow across user roles, goals, experience levels, and execution conditions. Check guests and paid users, or mobile and desktop screens, separately when their expected behavior differs.

Persona descriptions and goals provide context. Actual account permissions, authentication, locale, and viewport still need to be configured and used by the test. See Scenarios and personas.

Apply the three views together

Start with one executable flow, then associate the relevant capabilities and user conditions. Keep unverified areas visible as missing coverage. Review execution evidence in Reports and analytics.