Several looks for one check

GUI Test Studio keeps one expected version per browser, theme, screen or language, and each run uses the one you choose.

Why several looks

The same screen can rightly look different: in dark mode, on a laptop instead of a 4K monitor, on another version of Windows, in French instead of English.Instead of one test per environment, keep one test whose checks hold one expected version per environment.

Save

Default

as recorded

Save

Dark mode

a profile you add

Enregistrer

French

a profile you add

One check can hold one expected look per environment.Pick the profile when you run, and every check compares against its own version for it.
WordMeaning
DefaultWhat was recorded.Every run uses it unless you pick a profile.
Baseline profileA named environment you add: "Dark mode", "4K monitor", "French".
BaselineA check's expected version for one profile: a picture, a text, a shape or an arrangement.A step can hold a profile's version too.

Steps have versions too

A baseline is not only for checks.Every event can hold a profile's version of what it does: the words a Type Text types, the key a Key Press presses, the address an Open Web App opens, the program a Run App starts, the file an Upload File hands over.Where a step happens on the screen and when it happens are shared by every version.Under the French profile, the test types the French words; under the default, the recorded ones.

Name your profiles

Open Settings, Project Settings in either app, and add your profiles in the Baseline Profiles card.A profile is just a name; the checks fill it in over time.

In GUI Test Studio, Profiles... on a Baselines tab opens the same list in a small window, the Default profile first.The Default profile can be renamed there too.

Give a check its version

Two ways, use whichever is quicker.

  1. 1

    From a run (the quick way)

    Run the test with the profile selected, for example Dark mode.The checks without a dark version compare with the default and fail.In the report, Accept actual as baseline for Dark mode files each new look under that profile; the default stays as it was.

  2. 2

    In GUI Test Studio

    Select a check or a step, open its Baselines tab and select the profile.The panel now shows that profile's version; Capture... starts a screen capture with a ghost of the check's region drawn where it stood, and Capture the Same Region takes the profile's version from that very place.

    The preview has a Baseline chooser of its own: pick a profile there and the preview shows the test as it runs under it.

Choose the profile of a run

On a test's page in GUI Test Runner-Recorder, pick the profile in the Baseline row before clicking Run Test.The choice is remembered for that test on this computer.

  1. 1Baseline: Default, or one of your profiles
ExampleA nightly run per theme

Your pipeline runs the same tests twice a night: once with the default light look, once with the Dark mode profile.One test, two environments, every check comparing against the right version.

Keep them tidy

Make Default turns a profile's version into the default, for when the new look becomes the main one, and keeps the old default under the profile.Renaming or removing a profile in Project Settings updates every check of the test.

Still stuck?Tell us what you were trying to do, and we answer within one working day.Ask our team