Record related browser tabs and windows in one flow
TrueTest can record actions across eligible related browser tabs and windows as one continuous session. It preserves context transitions in Session Replay and in generated tests. Use this capability when an action in a tracked web application opens another tab or popup that remains part of the same task.
- You have purchased the TrueTest add-on.
- You have configured TrueTest Agent for the application under test (AUT). See Configure TrueTest Agent.
- Related-tab and window recording must be enabled for your AUT, and multi-tab and window playback must be available in Session Replay. Contact Katalon Support if you cannot access this capability.
- The primary tab and related contexts use the same configured AUT origin and TrueTest client.
Understand which tabs belong to a flow​
TrueTest treats a browser tab or window as related when the tracked main application opens it directly as part of the recorded workflow and it uses the same configured origin. Activity from an independently opened, duplicated, modifier-opened, cross-origin, or nested child-opened context remains separate.
The supported flow follows this pattern. Solid arrows show contexts opened directly by an action in the primary tab; dashed arrows show example switches between already-related contexts.
Record a related-tab journey​
- Start the tracked workflow in the primary application tab.
- Click the application control that opens the related browser tab or popup.
- Complete actions in the related context.
- Switch between the main tab and any already-related contexts as the workflow requires.
- From the main tab, open any additional related tabs or windows.
- Complete the remaining workflow.
TrueTest records the actions as one session and preserves each transition between the main tab and its related tabs. When you generate a journey map, the session appears as one end-to-end flow instead of separate disconnected flows.
Example: review an insurance claim across related tabs​
Consider an insurance case-management application that keeps a claim in the primary tab, opens a policy record in a related tab, and opens a document viewer in a popup window.
Browser actions​
- Open a claim in the primary Claim details tab.
- Click Review policy. The application opens the policy record in a related tab.
- Expand Coverage details.
- Click Confirm coverage.
- Return to the primary Claim details tab.
- Click Review documents. The application opens the claim documents in a popup window.
- Open Proof of loss.
- Click Mark reviewed.
- Return to the primary Claim details tab.
- Click Submit for approval.
Generated TrueTest flow​
TrueTest preserves the application actions and context transitions as one ordered flow:
Primary tab: Open Claim details
Primary tab: Click Review policy
Switch to Window1 (Policy record)
Window1: Expand Coverage details
Window1: Click Confirm coverage
Switch to primary tab
Primary tab: Click Review documents
Switch to Window2 (Claim documents)
Window2: Open Proof of loss
Window2: Click Mark reviewed
Switch to primary tab
Primary tab: Click Submit for approval
This example illustrates the expected ordering. Generated tests use deterministic window aliases such as Window1 and Window2 and include captured page-title comments to make context changes easier to review.
Review the recorded flow​
- Generate a journey map that includes the recording period. See Generate a new user journey map.
- Open the journey map and locate the related-tab flow.
- Click View test steps to review the actions and tab transitions.
- Open the Session replay tab, then click Play to review the recording when replay data is available.
Session Replay provides a header for each playable context and follows recorded context switches. It shows one active context at a time and does not display multiple tabs or windows simultaneously. Closing a related context is reflected when the browser provides enough opener information, but close detection is best effort.
When adding a verification, switch to the context that contains the target step. Verification authoring is available only for the active context.
If a stored flow was created before window metadata was available, regenerate the flow before regenerating its test case. TrueTest cannot reconstruct missing historical snapshots or page state.
Limitations​
- TrueTest merges only same-origin contexts opened directly by a tracked action in the main application tab. Manually opened, duplicated, Ctrl/Cmd-clicked, middle-clicked, Shift-clicked, and cross-origin contexts are recorded separately.
- Nested tabs or windows opened from a related context are not linked to the original session.
- Contexts opened with
noopener, or after the opener has reloaded, might not expose enough identity for linking or close detection. - Session Replay cannot reconstruct a context without a playable snapshot. A context that has no snapshot is omitted from the replay header.
- Generated tests require the browser runtime to expose one unique new window handle for each previously unseen window alias.