Flows represent your application users' behavioral patterns. While a user session shows the interaction path exercised by an individual user, flows represent the user paths across user sessions. Relicx continuously analyzes incoming user sessions to generate user flows automatically.
Flows provide you with valuable analytics and insights into how your application is used in the real world. The flow map view shows a familiar Sankey diagram to help you visualize how your users move around your application pages.
Flows also indicate the paths that need to be exercised by your End-to-End (E2E) tests simulate real user behavior in your pre-release testing.
You can drill into the user flows for an App by clicking one of the FLOWS buttons on the left side navigation bar.
Relicx automatically analyzes incoming sessions to look for similarities based on the entry point URL, pages traversed, and the navigation sequence to identify and extract flows. Flow extraction is an ongoing process. As such, new flows may be created over time.
After you instrument your app, user sessions should start appearing within a few minutes. The first set of flows should be generated within a few hours. Relicx needs to accumulate a certain number of sessions to make the flow extraction meaningful.
Each flow is characterized by the following
CX Coverage, to indicate its popularity or usage. For example, a flow with 5% CX-COVERAGE represents 5% of all your user sessions. The CX-Coverage metric can be used to measure a flow's business criticality and is represented by the width of the flow in the flow map.
Flow Sessions, are all user sessions that the flow represents. Not all user sessions are mapped to flows. A session is part a flow only when it is similar to the user interaction pattern of the flow.
Tests. Relicx automatically generates automated tests for each flow. Each flow will have at least one test generated for it. You can create additional tests by picking a member session and using the "Generate Test" option.