Troubleshooting

Try, in this order

1. 1Check that this screen has the same resolution and display scaling as the recording.Elements are compared at the size they were recorded.
2. 2The element may have moved outside its search area.Make the area larger, or tick Search Entire Screen.
3. 3The visual target may include something that changes, like a counter or a highlight.Draw its rectangle smaller, around the stable part only.
4. 4The screen may need longer to appear.Raise the check's timeout.

Try, in this order

1. 1Compare the screen resolution and display scaling of both computers.This is the most common cause.
2. 2Compare the theme (light or dark), the browser and its zoom level, and the language of the app.
3. 3If both looks are right, keep both with a baseline profile per environment.For another browser or device of a web app, generate a version of the test for it instead.

Try, in this order

1. 1Switch the report to Pulse or to the difference view: both light up what changed.It is often one character or one digit.
2. 2With AI Smart Verification on, read its verdict and its explanation of what changed.
3. 3If the difference is real but harmless, set the check's strictness to Relaxed, or accept the new look.

Try, in this order

1. 1Make sure a check stands just before the click: the click then follows the element wherever it is found.
2. 2Check that the window is where it was during the recording, at the same size.
3. 3Check the display scaling: at another scaling, every position on the screen changes.

Try, in this order

1. 1That value changes on every run.Turn the check into a Dynamic Text Assert, which checks the kind of value, not the value.

Try, in this order

1. 1Raise the Enhanced Accuracy Pass level of the test, in Project Settings: the check is then compared on the element's best moment.

Try, in this order

1. 1Replace fixed Waits with checks: a check goes on the moment the screen is ready.
2. 2Make search areas smaller: a small area is searched faster.
3. 3Switch on the graphics card in the Preferences, if the computer has one.

Try, in this order

1. 1Choose the text's language in the check instead of Automatic, especially for short words.
2. 2Set Recognition quality to Best.
3. 3Draw the search area a little larger than the text, so no letter touches its edge.
4. 4Keep the precision on Tolerant, which forgives look-alike characters and spacing.

Try, in this order

1. 1That is normal: saving is when the checks are created, one for each element you used and for what appeared.A long recording with Verify Text on takes longest.A progress bar shows each step.

Try, in this order

1. 1Turn on USB debugging in the phone's Developer options.
2. 2Use a data cable: some cables only charge.
3. 3Unlock the phone and tap Allow when it asks about this computer.

Try, in this order

1. 1Put your app back on the page and in the state it showed when the recording started, then click Try Again.
2. 2If the difference does not matter, click Run Anyway.
3. 3To skip this comparison on this computer, turn it off in the Preferences, on the General page.

Try, in this order

1. 1Open that branch in GUI Test Studio, from the Browsers & Devices panel.The steps that could not be done carry an amber corner, and the Properties panel says why.
2. 2An element the page hides on that screen, behind a menu GUI Test Studio could not open, is the usual cause.Fix the step on that branch, or record that part again.
3. 3After a change of your page, regenerate the branch.

Try, in this order

1. 1A test runs on the screen GUI Test Runner-Recorder is on, unless it was recorded on another monitor or its Project Settings name one.Open its Project Settings and change Run On: GUI Test Runner-Recorder's screen, the main screen, one monitor, or all of them.
2. 2A monitor the test was recorded on that is not connected is replaced by the main screen; the app asks first.
3. 3Before a recording, the app asks which screen the test uses; the Preferences' Recording Defaults keep the answer.

Try, in this order

1. 1A web page goes offline through its browser and always works.A program or the whole computer needs the small Windows service of GUI Test Studio.
2. 2Install GUI Test Studio for all users, as an administrator: the installer sets the service up.

Try, in this order

1. 1A test could not run: the console says why.Most often the screen differs from the recording, or the app under test has no window.
2. 2Fix the machine to match, or add --ignore-screen-mismatch or --ignore-missing-target when the difference is expected.
3. 3Run gtr-cli check on the folder to see every test's readiness without running it.

Try, in this order

1. 1The build agent must run in a signed-in, unlocked desktop session, not as a background service: a GUI test needs a real screen.
2. 2Switch off the screen saver, sleep and notifications on that machine.

Try, in this order

1. 1Click Open the Browser Again in the app.
2. 2Open the website yourself, sign in, and go to the address the app shows.Type the code there.
3. 3A code is valid for 15 minutes.If it is older, quit the app and start it again for a new one.

Try, in this order

1. 1This computer was deactivated on your account page, or you signed out in one of the three programs: they share one sign-in.Sign in again.
2. 2After a new installation of the apps, sign in once more: your seat is still yours.

Try, in this order

1. 1A new version is published.Update Now downloads and installs it, and the app starts again up to date; Later keeps the app as it is until its next start.
2. 2Only a critical update must be installed before the app goes on: the message says so.
3. 3On a computer without a browser sign-in, Open the Download Page gives you the installer; a build machine's command-line runner says the same and waits for the update.

Try, in this order

1. 1Read the reason it gives.A trial or a subscription that ended: choose a plan on your account page, then click Try Again.
2. 2If you are a member of a team, ask its owner: the plan may have ended, or your seat may have been removed.

Try, in this order

1. 1On your account page, under Your computers, deactivate the computer you no longer use.
2. 2If you own a team, remove a member or a key you no longer need, or add users to your plan.

Try, in this order

1. 1A seat moves to another computer at most once every 30 days.The message gives the date it can move again.
2. 2Until then, use the computer you signed in on before.
3. 3If that computer is lost or broken, write to support and we free the seat.

Try, in this order

1. 1Look in the spam folder.
2. 2Ask the owner to click Send again beside the invitation, on their account page.
3. 3Sign in with the very address the invitation was sent to: another address is refused.