|
General Description
The screen saving [and validation] facility is intended
to permit saving and validating files containing the contents of
text areas,
parts of images,
complete images,
the client area of an application (including the eValid browser face)
or the entire window of an application
(including the entire eValid browser window).
File Name Selection
During script recording (see below) the user is asked to provide
a unique identifying key that is used as part of the filename into which data is stored.
The user-supplied filename identifier, "unique_id" is shown in the commands described below, which also indicate the name of the file created.
Material saved during the eValid recording process is put into a set of baseline files named as follows: scriptname-B.unique_id.txt, scriptname-B.unique_id.bmp or scriptname-B.unique_id.gif, etc... In case the user-supplied identifier has already been used, text files are appended, but bitmap files are overwritten.
During script playback, text and image data is saved in response files named as follows: scriptname-R.unique_id.txt, scriptname-R.unique_id.bmp or scriptname-R.unique_id.gif, etc...
These commands use the eValid eVimagediff utility to compare files during playback. If the reponse file does not match the baseline file according to the comparisons made by eVimagediff that step of the playback results in an error message.
Command Descriptions
There are different recording commands that
result in various script commands depending on the choice of
object to process and how to dispose of it.
eValid: Record > Save > Selected Image
eValid: Record > Validate > & Save > Selected Image
Recorded script command syntax:
SaveSelectedImage wid "unique_id" idx ""
[creates scriptname-R.unique_id.gif]
ValidateSavedSelectedImage wid "unique_id" idx ""
[creates scriptname-B.unique_id.gif]
eValid: Record > Save > Selected Text
eValid: Record > Validate > & Save > Selected Text
Recorded script command syntax:
SaveSelectedText wid "unique_id" idx position length ""
[creates scriptname-R.unique_id.txt]
ValidateSavedSelectedText wid "unique_id" idx position length ""
[creates scriptname-B.unique_id.txt]
eValid: Record > Save > Screen Rectangle
eValid: Record > Validate > & Save > Screen Rectangle
Recorded script command syntax:
SaveScreenRect wid "unique_id" width height x-offset y-offset
[creates scriptname-R.unique_id.bmp]
clValidateSavedScreenRect wid "unique_id" width height x-offset y-offset
- or -
ValidateSavedScreenRect wid "unique_id" width height x-offset y-offset
[creates scriptname-B.unique_id.bmp]
eValid: Record > Save > Window Face
eValid: Record > Validate > & Save > Window Face
Recorded script command syntax:
SaveWindowFace wid "unique_id"
[creates scriptname-R.unique_id.bmp]
ValidateSavedWindowFace wid "unique_id"
[creates scriptname-B.unique_id.bmp]
eValid: Record > Save > Window
eValid: Record > Validate > & Save > Window
Recorded script command syntax:
SaveWindow wid "unique_id"
[creates scriptname-R.unique_id.bmp]
ValidateSavedWindow wid "unique_id"
[creates scriptname-B.unique_id.bmp]
Implementation Note
Commands that refer to the "window face" assume that eValid has
direct access to the pixel values on the screen face.
When the information on the face is not available eValid will act to
bring that part of the screen into focus, or to de-minimize it if possible.
In some modes of playback operation, when for whatever reason
the browser screen is not available, eValid is unable to successfully
validate and/or synchronize.