Choose what a test verifies
The question after every recording: visual elements, text, and what appears on screen.
The question
When you stop a recording, GUI Test Runner-Recorder asks what this test should verify.Your answer decides which checks the test gets by itself when it is saved.You can always add, change or remove checks afterwards in GUI Test Studio.
Verify Visual Elements
On by default.Every element you click or type into gets a visual check just before your action: the test makes sure the button, field or menu item is on screen and looks right, then performs the click.
A missing icon, a button in the wrong colour, a broken image, a label that turned lowercase, an element that disappeared after a release.
Wait up to is how long a run waits for the element to appear before the check fails.5 seconds suits most apps; raise it for a slow page.
Verify Text
Off by default.When it is on, the words you click on are checked as text, read from the screen.A text check passes when the words are right, even if the font or the colour changed.
| Option | What it means |
|---|---|
| Wait up to | How long a run waits for the text. |
| Changing values (date, time, currency) | What to do with a value that differs on every run: check its exact value, check only its format ("a date", "an amount"), or keep a picture of it instead. |
| Recognition quality | Balanced reads quickly and well.Best is the most careful, Fast the quickest. |
Your app shows today's date at the top.Its exact value fails tomorrow.Pick "Their format" and the test checks that a date is shown, whatever the date.
Verify What Appears
On by default.Some screens appear without being clicked: a menu opens, a dialog pops up, a confirmation message shows.These get checks too, placed at the moment the screen settled, so the test confirms they really appeared.
Its options
| Option | What it means |
|---|---|
| Group Asserts | Everything that appeared is checked together, as one group per screen. |
| Layout Asserts | Also checks that the elements stand where they belong, so a misplaced or overlapping element is caught. |
| Detail | How much of what appeared is checked: from only the main elements to almost everything.Pick a level on the row of five small screens, from big changes only to every change. |
| Advanced: Elements checked per screen | The most elements checked each time the screen changes.Automatic follows Detail; a higher number checks more of a crowded screen and makes runs longer.When a screen holds more, pictures and texts each keep their share. |
How many elements are checked per screen
Each time the screen changes, the test checks a limited number of the elements that appeared.Under Advanced, Elements checked per screen sets that limit.It starts on Automatic, which follows Detail: 5, 8, 12, 20 or 32 elements, from the lowest level to the highest.
When a screen shows more elements than the limit, pictures and texts each keep their share: the largest pictures and the first texts in reading order.The rest of that screen is not checked.
| Your screen | What to choose |
|---|---|
| A menu, a small dialog, a confirmation message | Keep Automatic.It already covers everything on such a screen. |
| A long form, a settings page, a table with many rows | Increase it, for example to 30 or 40, so the fields and rows further down are checked too. |
| A dashboard with many cards, badges and icons | Increase it, so the icons and badges are checked beside the labels. |
| A screen where every label matters, such as a price list or a translated page | Increase it, up to 100, to check all of them. |
| Tests that must run fast, or an app whose screens change often | Keep Automatic.Every extra element makes each run longer and is one more thing to update when the app changes. |
Why it is useful: one number decides how thorough these checks are, without changing which screens are checked.That stays with Detail.
Make it your default
Tick "Don't ask again" to keep these choices for every recording and skip the question.The same settings live in Settings, Preferences, Recording Defaults, where you can change them, and the General page brings the question back.
Closing the question in any way keeps the choices as shown: a recording is never lost to a question.Next: open your test in GUI Test Studio.
Still stuck?Tell us what you were trying to do, and we answer within one working day.Ask our team