Every browser and device from one recording
Record a web test once and run it in Chrome, Edge and Firefox, on phones, tablets and screen sizes, in other languages and on slow networks.
Record once, test everywhere
Record a web test once, in the browser you use every day.GUI Test Runner-Recorder then makes the same test for every browser, device and orientation you choose: Chrome, Edge and Firefox, iPhones, Android phones and tablets, laptop and desktop screen sizes, held upright or sideways.
Each one is a version of the recorded test, called a branch.A branch performs the same steps on the same page, but through the page's own elements: it clicks the button where that browser and that screen show it, not where it stood in the recording.Its checks are cut again from what that device really shows.
Choose the browsers and devices
When you record a web app, tick Also generate this test for other browsers and devices under the address.The choices open below it.
| Choice | What it means |
|---|---|
| Browsers | The browsers installed on this computer.The one you record in is always included. |
| Devices | Phones, tablets and desktop screen sizes, grouped by maker.Type in the search field to find one by name or size, such as galaxy, iphone 15 or 1920. |
| Orientation | Portrait, landscape or both, for each phone and tablet, or for all of them at once. |
| Language, Network, Zoom | Conditions the page runs under, explained below. |
A box in a list's heading ticks every row of it, and a group's box ticks every device under it.Under the lists, the window says how many tests that makes, how long they take to make and how much disk they use.When running them all one after the other would take more than an hour, a note says so.
Once the test is saved, the branches are made at once, in the background.A small card at the bottom right of the screen shows how far it is, and Cancel stops after the current one: every branch already made is kept.The message after saving says how many were made and how many need your attention.
Language, network, zoom and motion
The Language, Network, Zoom tab adds conditions.Each condition you tick is a branch of its own, combined with the browsers and devices you chose.The first row of each group is the page as it is.
| Condition | What the page gets |
|---|---|
| Language and time zone | The browser's language and the clock of a city.A page that translates itself shows that language, and dates and times appear the local way. |
| Network speed | Fast 4G, Slow 4G or 3G: the page loads as slowly as on that connection.Only Chrome and Edge can slow their network, so Firefox is left out of these. |
| Zoom | The page enlarged from 100 to 200 percent, as someone who needs larger text sees it. |
| Reduced motion | The setting that asks pages for fewer animations. |
Tick Français (France) and Slow 4G with an iPhone.The branch checks the French page, at the speed of a weak connection, on the phone's screen.Its text checks expect the words the page shows in French.
What each version does
A branch is made by replaying the recorded test on that browser and device, step by step, and writing down what it took.
| On the page | What the branch does |
|---|---|
| An element stands somewhere else | It clicks it where it is, at the point the page says belongs to it. |
| An element is below the fold | It adds a Scroll to step that brings it into view. |
| An element sits in a menu | It adds the step that opens the menu first, and closes it again when it covers what comes next. |
| A check's element looks different | It cuts the check's picture again from that device's screen. |
| The page shows a text in another language | The text check expects what the page says there. |
| A file is chosen | It hands the file to the page, without the system's file window. |
| An element is not shown on this device at all | A check of it is left out, with the reason. |
A branch is ready when every step found its element.When a step could not be done, the branch needs your attention: open it in GUI Test Studio, where the step carries an amber corner and the Properties panel says why.
Without a browser window
A branch can run headless: the browser works without a window, so nothing appears on the screen and the computer stays yours while it runs.Phones, tablets and branches with a condition always run this way.Desktop branches do too when the test allows it, which is on by default.
The switch is in the test's Project Settings, in the Web App card, in both apps.A test whose steps act on something the page cannot see, such as another program's window, runs with a window, and the setting says why.
Run them
Click Run Test on a web test that has branches, and GUI Test Runner-Recorder asks which ones this run covers.
- 1
Tick the runs
Every generated branch is ticked.Untick what you do not need this time, or tick a whole device or group at once.A branch that is not generated yet is greyed out.
- 2
Check the expected time
The time under the list comes from how long each one took last time, and from the test's length for one that never ran.It is a typical figure: a check that waits for something slow can make a run longer.
- 3
Run
The branches that need no window run side by side, up to four at once depending on your computer, and the others one after the other.At the end, one window lists every run's verdict, each with its report.
Running them side by side is a setting: Settings, Preferences, General, and the switch in the run question.
See and edit them in GUI Test Studio
A web test with branches gets a Browsers & Devices panel in GUI Test Studio's left column.It draws them as a tree: the recorded test, then each browser, each device, each orientation, every one with its state and the result of its last run.
| To | Do |
|---|---|
| Move around | Drag the background, turn the wheel to zoom, or use the fit button.A button switches the tree between top-down and left to right. |
| Open a branch | Double-click it.The timeline shows that browser and device, with its own pictures and steps. |
| Act on several | Ctrl+click them, or select a browser or a device to act on everything under it. |
| Make them again | Regenerate, Generate, Add Browsers and Devices... and Remove... sit under the tree. |
An edit on one, or on all
When you save a branch after changing what a step does, GUI Test Studio asks whether the change is for every browser and device, or for this one only.A change of a picture or a moment always stays with the branch.
When you save the recorded test after changing what its steps do, it offers Update Every Browser and Device, which makes every branch again from it, or Keep Them as They Are.
Run one from GUI Test Studio
The arrow beside Run Test offers Save & Run One Browser or Device, then Save & Run Headless (No Browser Window) and Save & Run With a Browser Window for a run you want to watch.
Their reports and history
Every branch is a test of its own when it comes to results: its report, its run history, its video.In the Confidence Report, the Browsers & Devices button lists the recording and every branch with its last verdict, and opens the report of the one you pick.
From the command line
gtr-cli runs branches too.gtr-cli info lists a test's branches with the name each one goes by on the command line, and the Command Line & CI/CD window offers them in a list.
gtr-cli run Checkout.GTS --branch all --junit results\junit.xmlgtr-cli run Checkout.GTS --branch msedge__iphone-15__portraitgtr-cli generate Checkout.GTS --branch missing| Option | What it does |
|---|---|
| --branch | all, recorded, one name, or several names separated by commas. |
| --headless on | Run without a window wherever the test allows it. test keeps the test's own choice, off always shows the browser. |
| --parallel off | Run the branches one after the other instead of side by side. |
A runner test can carry every generated branch.See Run tests in your pipeline.
Still stuck?Tell us what you were trying to do, and we answer within one working day.Ask our team