eValid™ -- The Web Quality Suite Browser-Based Client-Side Functional Testing and Validation Page Timing/Tuning Transaction Monitoring. WebSite Spidering & Analysis and Realistic Server Loading.

Introduction
Here are selected eValid resources to support recording and playback of applications that run on the desktop.

Application Mode/Desktop Mode Capabilities
Here are some pointers to the basic support eValid provides for desktop mode operation:

• Application Mode Operation -- Basics of Application Mode
• Desktop Mode Operation -- Basics of Desktop Mode
• Desktop Access Modes -- How eValid handles desktop interactions
• Validate & Synchronize Screen Rectangle Command -- Details of the screen synchronization command.

Worked Desktop Examples
Here are some fully worked examples that show how desktop mode operates:

• Simple Browser + Desktop Examples:
  • Notepad Example -- Most likely to work on foreign system because Notepad is "constant".
  • Wordpad Example -- Works OK, but there are some variations in different versions of WordPad.
  • Word Example -- Works OK but there are many varieties/versions of Word.
  • Baseline Notepad Example -- Demonstrates image sync AND baseline file comparison.
    Baseline Notepad Recording Screenshot Sequence -- The full sequence of eValid commands showing how the above example was completed.

• Complex Browser + Desktop Examples:
  • PDF File Recording Example -- How do handle an on-screen PDF file.
  • File Download Modal Dialog Recording Support -- How do handle a modal dialog.

Desktop Command References
The eValid commands that pertain specifically to desktop operations are all found in one section of the script definition file: Keyboard and Desktop Operations

Additional Resources
Several additional resources are available to support pure-desktop operations:

• The ValidateClipboardText command can be used to confirm the content of anything that can be "scraped" from the desktop into the clipboard.
• The SystemCall and SystemCallWait commands can be used to invoke outside resources from within a test script playback.
• The TabKey and EnterKey can be used to inject the corresponding desktop events into the playback environment.
• The SaveWindow and SaveWindowFace apply to non-browser windows when the playback is in application mode.
• The TouchFile command can be used to force update of the most-recently-viewed data in a file structure. If the file can't be found it will be created and touched, assuming that the playback process has the correct write permissions.