seckey wrote:What about screen minimized screen validation. Can eValid do that or do you have to have a screen to read from?
The answer to that depends on what kind if validation you're doing.
(1) If you are talking about validation based on DOM values, for example with a "ValidateSelectedText" command, then it doesn't make any difference whether the browser occupies land area on your desktop or not because the validation is done by eValid with direct retrieval of the DOM values for the text to be matched.
eValid can do this without needing any screen area becuase it looks "behind the screen" (in a way) by reading what the browser put up for you to see.
This can also work with non-visible information about a page. You could use a "ValidateSelectedObjProperty" command to read and check the value of ANY atrribute of any element anywhere on the page, visible or not.
(2) On the other hand if you are talking about what has been painted onto the desktop by the browser, then you do need to have the browser visible to do the comparison.
eValid does screen validations by reading the pixel values from the screen in the selected area and comparing the checksum of all of these values with what is recorded as the required checksum -- the value that is recorded in the script.
At the time eValid does the validation if there is not screen then the values it would read won't ever match up with the right values and the valuation will always FAIL.
-The eValid Team