Run a test

Start a run

1. 1

   Open the test

   In GUI Test Runner-Recorder, click a recent test on the home page, or Open a Test....

2. 2

   Prepare the screen

   Put your app in the state the test starts from, exactly as when you recorded it.

3. 3

   Click Run Test

   The test's page holds everything about it: its name and file, how many steps, checks and Scenarios it has, and the buttons Run Test, Edit in GUI Test Studio, Confidence Report, Project Settings and Record New.Under them, the Runs card lists every past run.

   12

   Enlarge

   1. 1Run Test
   2. 2Runs: every past run, newest first

The Runs card

Each row is one run: when it ran, its result, how long it took and how many checks passed.The newest is on top, and the line above the list sums it up.Double-click a run to open its Confidence Report exactly as it was; Confidence Report opens the newest one.

During the run

GUI Test Runner-Recorder steps aside and counts down, then the test moves the mouse, clicks and types by itself, checking the screen at every step.

Enlarge

While the test runs, a thin blue TEST RUNNING banner stands at the top of the screen, with the key that stops the run.It is never in a picture the test takes, and your clicks pass through it.To hide it, turn off Show the Test running banner during a run in Settings, Preferences, General; from the command line, --run-banner off does the same.

A run stops at the first check that fails, unless that check is set to continue the test.Then the Confidence Report opens and tells you what happened.

Questions before a run

When something about this computer differs from the recording, the app asks before it starts, so you know why a run might fail.

Is the screen where the test starts?

Right after the countdown, GUI Test Runner-Recorder compares your screen with the first moment of the recording.If your app shows another page or another state, nothing runs.The app comes back with both pictures, where the test starts and your screen now, and marks what differs.Put your app back where the test starts and click Try Again.

When the difference does not matter, Run Anyway starts the run as it is.To skip this comparison for good on this computer, turn off Check that the screen is where the test starts before each run in Settings, Preferences, General.A web test that opens its own browser, and a run without a window, are never held to it.

Several monitors: where the test runs

A test runs on the screen GUI Test Runner-Recorder is on, and the browser or app it opens appears there too.A test recorded on another monitor, or on all of them, keeps running there.Run On, in the test's Project Settings in either app, changes that: the screen GUI Test Runner-Recorder is on, the screen it was recorded on, the main screen, one monitor you pick, or all screens.The monitor you pick lights up for a moment.

What the test clicks and checks moves with it: a test recorded on one monitor and run on all of them is placed where that monitor stands, and one recorded on all screens and run on one keeps what stood on that one.The windows the test opens itself go onto its screen too.

From the command line, --screen does the same: here (the terminal's screen), recorded, main, all or a monitor's number.See Run tests in your pipeline.

Run from GUI Test Studio

While you edit, Run Test in GUI Test Studio's toolbar saves the test and opens it in GUI Test Runner-Recorder, which asks you to click Run Test once your screen is ready.

Start in the middle

On a long test, working on its last part, put the playhead where you want to start and choose Save & Run From Playhead Position (Shift+F5).Put the app in the state it had at that moment, and only the steps from there run.F5 runs from the start.

A web test with several browsers and devices

In GUI Test Runner-Recorder, Run Test on such a test asks which browsers and devices the run covers: the recording and every version made for a browser or device, as a tree, every generated one ticked, with how long they are expected to take.The ones that need no browser window run side by side, the others one after the other, and one window lists every verdict at the end.In GUI Test Studio, the arrow beside Run Test runs just one of them, with or without a browser window.See Every browser and device from one recording.

Runs that pass every time

Where the results go

Every run is kept in the results folder inside the test's own folder: its report, its video and its history entry.Open the test again later and the Runs card lists them all; Confidence Report shows the last run exactly as it was, and a double-click on any row shows that run's.

Next: Read the Confidence Report.