Skip to main content

Generate user journey

Last updated: August 2026

After setting up the traffic agent, TrueTest collects and models user journeys that will in turn enable the generation of relevant flows.

TrueTest uses the MutationObserver API and Javascript Listener to track user interactions on the AUT, such as clicks, inputs, and selections by monitoring changes to the DOM and attaching a listener to DOM elements. The technology combination allows TrueTest to collect detailed data on user behavior. TrueTest then uses the data to generate user journey maps in your AUT.

To view the list of application domains with generated user journey map, on the TestOps navigation bar, click TrueTest.

TrueTest journey maps in TestOps

You can click the ID of a map or View details to access its detail page. The detail page includes user flows. See: View user journey map.

Generate new user journey map​

You can generate a new user journey map with different time frame.

On the User Journeys page, click Generate New User Journey Map and select a time period, or customize your preferred time period.

Generate journey maps in TestOps G3

Filter map data​

The filter options allow you to generate specific flows that focus on functional areas.

  • Filter by user session attributes: Filter sessions using a text-based query, e.g. userRole, flow.
  • Filter by URL keywords: Filter sessions based on the URL patterns, e.g. "checkout", "product-details".

Advanced settings​

  • Carry over existing assertions: Enabled by default. When this option is enabled, TrueTest can reuse assertions from previous maps. Assertions are carried over when:

    • They are marked Apply to similar flows. Learn more in Add assertion to test steps.
    • The matching flow does not already have a test case.

  • Ignore previous flows and overwrite existing test cases: When this option is selected, all new flows are generated independently of the previous map, and the list will display New flows only. When not selected, TrueTest will compare all new flows from the new map with the previous map to determine the Flow Status.


The user account that triggers a map generation will receive a notification email when it is finished.

Retry a failed journey map generation​

You can retry an eligible failed journey map from its own row. TrueTest restores the saved configuration for that specific failed attempt, including its tracking environment, date and time range, session attribute filter, URL keyword filter, and advanced settings.

  1. On the Journey Maps page, locate the failed journey map you want to retry.
  2. Click Retry for that row.
  3. Review the restored settings in the journey map dialog. Update any settings that are no longer valid.
  4. Submit the retry request.

After TrueTest accepts the retry, it archives the selected failed attempt and adds a new journey map entry for the retry. If the retry fails, the new failed entry remains available for another retry while its saved configuration is valid.

note

The Retry action appears only for failed journey maps that still have a saved generation configuration and can be retried in the current project and tracking environment.

View user journey map​

From the map list on the User Journeys page, you can click the ID of a map or View details to access its detail page.

View map details in TestOps G3

A user journey detail page has two sections: visualized map and flows.

View visualized maps​

Here you can find user journeys visualized as a map. The map contains pages and actions representing connections from the source pages to the target pages. You can:

  • Select a flow to highlight it in the map.
  • Click and drag the pages to re-organize the map.
  • Switch on the Highlight traffic volume toggle to see the amount of user activity.
  • Double-click on the page to edit page information.
Perform actions with user journey map G3

Show most or least-visited pages​

Use the page ranking controls above the graph to focus the journey map on pages with the highest or lowest traffic:

  1. Select Top to show the most-visited pages, or select Bottom to show the least-visited pages.
  2. Select the number of pages to show.

The ranking uses the active journey map filters. When you select Bottom, pages are ranked from least visited to more visited. Select Top to restore the existing most-visited page view.

Select a page node to view its user session count. TrueTest uses the page-level session count from the generated map, so the value remains the same when you switch between normal and traffic-highlight modes or change the Top or Bottom ranking display for the same map.

View flows​

A flow represents an end-to-end path performed by a number of users on the AUT. For example, a common flow on e-commerce applications is: View a product > Add it to cart > View cart > Complete checkout.

A user journey map can have a number of different flows. Click View test steps to see more details of a flow. Click Edit flow info to update the summary or description.

Use the toggle in the upper-left corner to switch between viewing as a branching structure and viewing as a list.

View and edit flow in G3

Edit flow steps before generating a test case​

You can mark captured steps as deleted before generating or re-generating a test case. The deleted steps remain visible in the flow for review but are excluded from the generated test script.

  1. Click View test steps to open the flow details.
  2. In Test Steps, hover over the step you want to delete, then click the minus icon. The icon tooltip is Delete test step.
  3. Confirm the deletion. If the flow has a linked test case, the confirmation dialog warns that re-generating the test case overwrites its generated script.
  4. Review the deleted step. TrueTest strikes through the step and any verification attached to it.
  5. In the unsaved-changes banner, click Save changes to save the edited flow, or click Discard to revert the pending changes. The banner summarizes affected verifications, custom scripts, and deleted steps.

Click Undo on a deleted step to restore the step and its attached verification. You can undo a deletion before or after saving the flow.

The following demo shows how to delete a flow step and save the change:

note

Editing a flow does not change the original captured session or Session Replay history.

User session replay (beta)​

Click Replay session (beta) to review the original user journey behind an AI-generated test. By replaying recorded sessions, you can:

  • Debug unclear test flows
  • Identify locator-related failures
  • See exactly which elements were interacted with

Session Replay supports long and high-event sessions, helping you review complex journeys with fewer unavailable or incomplete replays.

Flow filters​

You can filter the flows by their sources, traffic levels, number of test steps, and flow popularity.


  1. Tags - Filter or search flow using the Is or Is Not operator. See Tags.
  2. Source – Filter flows by what source they are generated from: User session or Manual execution.
  3. Traffic – Indicates the relative volume of user sessions that go through a particular flow. Learn more at Traffic levels.
  4. Status – Narrow flows by their stability status. See Flow status.
  5. Flows – Filter flows with or without test cases.
  6. Steps - Filter flows by specifying whether the number of steps is greater than, less than, or equal to a given value.
  7. Modifications – Filter flows by With assertion, Without assertion, or With test step deleted.
  8. Top Flow % – Focus on the most frequently used flows by selecting a percentage range (e.g., top 100%, 50%).

Manage visible columns​

Use the Columns control at the end of the filter toolbar to choose which columns appear in the flow list.

  1. Click Columns to open Manage Columns.
  2. Search for a column or select and clear the available column checkboxes. The flow list updates while preserving the current filters, sorting, and page.
  3. Click Reset to default to restore the default column set.

Required identifying columns and row actions remain available so you can continue to identify and work with each flow.

The Test Cases column shows whether test cases have been generated for each flow.
To export the flow data, click the Export icon. Exported flow and map files include additional metadata for analysis and reporting.

Tags​

Use the Tags filter to group flows by specific criteria such as features, scenarios, or teams. You can then filter or search flows using these tags to focus on what matters most. The Tags filter supports the operators Is and Is Not, and you can select multiple tags to include in each flow.

  • You can add tag individually or in bulk from either the Map View or List View.
    • The maximum tag length is 30 characters.
    • Tags are case-insensitive, and support the following characters: a–z, A-Z, 0–9, hyphen - and underscore _
    • Flow tags are independent from test case tags. They are not automatically transferred when generating test cases.

Flow status​

From the second journey map generation onwards, TrueTest categorizes the flows as stable, new, or obsolete to simplify the review process.

  • Stable: Flows with no changes that present in both the new and previous maps. Test artifacts remain intact and you can skip reviewing these flows.
  • New: Flows that did not exist in the previous map and require review.
  • Obsolete: Flows that appear in the previous map but are no longer in the new map. See more: Retain obsolete flows.

Generate test cases​

After TrueTest has identified the flows from user interaction, you can decide which flows are relevant to generate test cases. In the Flow section, select the flow and click Generate Test Cases.

If you already know which captured sessions you want to automate, you can also generate test cases directly from User Sessions before reviewing or generating a full journey map. See Generate test cases from User Sessions.

Before generating a test case, save any flow edits. TrueTest generates the test script from the latest saved flow and excludes steps marked as deleted.

Re-generate an out-of-sync test case​

When you save an edited flow that has a linked test case, TrueTest marks the test case as out of sync. A red indicator appears next to the test case ID in the flow details and on the flow list. Hover over the indicator to see: Test case is out of sync with the flow. Regenerate to update.

Trigger test case generation again from the flow to update the linked test case. Re-generation:

  • Overwrites the generated test script with the latest saved flow. Manual edits to the generated script might be lost.
  • Recomputes variables that TrueTest generated from the flow.
  • Preserves existing test objects so that manual updates to those objects are not overwritten.
  • Keeps the same linked test case and repository location.

The out-of-sync indicator clears after re-generation succeeds.

Once the test case generation has finished, you can revisit the flow and click View test case to view its details.

The generated test cases are stored in the registered script repository. Test case names are automatically generated based on the flow.

After re-generation, review the generated changes before using the updated script in your test project.

View generated test cases

Retain obsolete flows​

You can review obsolete flows which already have correspondingly generated test cases and decide which to keep or archive. For obsolete flows, TrueTest will archive within the Git repository.

A use flow is tagged as Obsolete in the following cases:

  • The features related to those flows no longer exist in the application
  • The application has been updated to introduce new flows
  • No users follow the flows during the data collecting period

Follow these steps to retain and archive obsolete flows.

  1. In the User Journey Map section, click the Review obsolete flows warning icon of the relevant map.

    Click review obsolete flows

  2. The Review Obsolete Flows window appears. Select the checkbox of the flow you want to archive, then click Archive selected flow(s).

    Select flows to archive

    A dialog appears to confirm your action. Select Archive and finish.

    Archiving flows confirmation dialog

  3. If you don't want to archive any, select Retain All.

Was this page helpful?

Table of Contents