Web flows do not always stay in one tab, or even one browser. Applications open links in new tabs, spawn popups, and some end-to-end tests need two independent browsers signed in as two different users. The Web Recorder handles all of this: tabs within a session, and multiple independent browser sessions, both recordable and both fully supported in your logic.
Working with Browser Tabs
As you navigate in the recorder, your application may open additional tabs or windows. When that happens, a Browser Instances icon appears in the recorder header. Click it to see every open tab, and select one to load it in the recorder browser.
Switching is recorded when recording is on. With the recorder in Fluid or Intent mode, selecting a tab from the list automatically records a switch-to-tab statement, so your logic reproduces the same navigation. With the recorder OFF, you can switch freely without recording anything.
Note: A popup emerging from an existing browser window counts as a tab within the same session. It does not create a new driver session.
Tab Commands
Beyond recording, these commands are available for tab handling in your logic:
| Command | What It Does |
|---|---|
| Load URL in tab | Load a URL in the current tab or open a new one |
| Switch to main browser tab | Return to the original tab |
| Switch to browser tab at index | Switch by the tab's position |
| Switch to browser tab based on URL | Switch by full or partial URL match |
| Switch to browser tab on title | Switch by the tab's title |
Working with Multiple Browser Sessions
Some flows need more than one independent browser, each with its own cookies and session data:
- Two user accounts signed into the same application simultaneously (a maker-checker approval, a buyer and a seller)
- Multiple independent applications in one end-to-end flow
- Comparing behavior across two separate browser instances
Each driver session manages its own browser window and session data, and can hold multiple tabs of its own.
Session Commands
| Command | What It Does |
|---|---|
| Initialize new Driver session | Open a new browser under a named handle ("default" for single-session tests) |
| Switch to Driver session | Make a previously created session the active one, by name |
| Terminate Driver session | Close a session and free its resources |
How Sessions Behave
- One session is active at a time. Switch to the session you want before executing logic against it; statements always run on the active session.
- Sessions end with the test case. By default, ACCELQ terminates all driver sessions at the end of every test case, unless the Browser Keep-Alive flag is enabled for the Run.
- Single-browser tests stay simple. For ordinary tests, a single "default" session is all you need, and you never think about session management.
Comments
0 comments
Please sign in to leave a comment.