Skip to main content

Generate user journey

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.

  • 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.

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

The user account that triggers to generate a new map will receive a notification email when the generation is finished.
A user journey map contain several flows built from user interaction with the AUT. You can select the flows to generate test cases.

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

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 could have a number of different flows. To quickly view the test steps of a flow, click the see more arrow. Click Edit flow info to update the summary or description of a flow.

View and edit flow in G3

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

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


  1. Source – Filter flows by what source they are generated from: User session or Manual execution.
  2. Traffic – Filter flows based on traffic levels.
  3. Status – Narrow flows by their stability status.
  4. Flows – Choose to display flows with or without test cases.
  5. Steps - Filter flows by specifying whether the number of steps is greater than, less than, or equal to a given value.
  6. Top Flow % – Focus on the most frequently used flows by selecting a percentage range (e.g., top 100%, 50%).

The Test Cases column shows whether test cases have been generated for each flow.
To export the flow data, click the Export icon.

Traffic level​

Traffic level indicates the relative volume of user sessions that go through a particular flow. It is a good practice to test all flows regularly.

There are four levels based on the percentage of the highest traffic volume observed:

  • High traffic flows: The most common use flows in your application. It means many users follow this path. For example, a highly common flow can be users logging in and checking their order history.
  • Medium traffic flows: Common flows but not as heavily used as high traffic flows. For example, users browse products and then leave the site.
  • Low traffic flows: Flows with fewer users, for example, users adding products to a wishlist.
  • Trivial traffic flows: The least common paths that users take. For example, contacting support on an e-commerce site might happen less often in some cases.

Tags​

Use the Tags filter to view flows associated with specific flow tags. You can select multiple tags to include or exclude flows.

  • Supported operators: Is, Is Not.
  • The maximum tag length is 30 characters.
  • You can select more than one tag at a time to view all flows that match any of the selected tags (for example, flows tagged with checkout or payment).
  • Flow tags are independent from test case tags. They are not automatically transferred when generating test cases.
  • In the List view, you can check the tags assigned to each flow in the Tag column.

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 decided which flows are relevant to generate test cases. In the Flow section, select the flow and click Generate Test Cases.

Click Generate test cases in G3

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.

View generated test cases

Retain obsolete flows​

You can review obsolete flows which already have correspondingly generated test cases and decide which to keep. 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 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 keep, then click Retain at the lower right of the window.

    Select flows to retain

    A dialog appears to confirm your action. Select Proceed.

    Retain flows confirmation dialog

  3. If you don't want to keep any flows, select Archive All.

Result​

The selected map is updated with the retained flows. Flows that are retained will have the Retained status.

Was this page helpful?