iefans wrote:Is there any general rule you use in deciding which test scripts to put into monitoring mode?
From the user perspective, we generally choose those scripts which are going to be the MOST indicative of correct ior reasonable or acceptable performance and behavior. Such tests can have a robust set of validations and associated timing limits and measurements.
From a technical perspective, we generally want those tests that are "desktop safe", so that we avoid any desktop contention issues that would require additional test scripting. When desktop safe the playback can occur without having to have the eValid browser use up any of the available desktop area -- the test can be run with the browser minimized, and that contributes to efficiency and accuracy in timing data.
The eValid Team