Can't Put In "Monitoring Mode"

[cahost2]

Is there any kind of test that you can't put in "monitoring mode"?

[eValid]

Is there any kind of test that you can't put in "monitoring mode"?

We generally recommend that a test be made fully self-synchronizing, so that when it is running from the command line (in the background) that it won't have an erroneous "fail to sync".

Also, tests that involve use of the desktop -- a file download or a "store this data in this local file" kind of action -- work fine but have to be run with exclusive access to the desktop. You could use the Lock and Unlock commands to do this, or you could simply make sure that tests which need desktop access never run in parallel.

You can confirm a test does NOT need the desktop by loading the script in the script window, opening the dashboard, minimizing the eValid browser, and running the test from the dashboard. If the test script needs the desktop the eValid browser will "restore". So if you get to the end and eValid finishes fully in minimized mode you are 100% OK for parallel monitoring mode.

eValid Support