SilkPerformer Citrix Tutorial - Borland Technical Publications
SilkPerformer Citrix Tutorial - Borland Technical Publications
SilkPerformer Citrix Tutorial - Borland Technical Publications
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
2 CREATING TEST SCRIPTS<br />
Trying Out a Generated Script<br />
Value strings (keyboard input) are visualized onscreen as floating red text until<br />
target window captions are identified (in subsequent nodes) to indicate where<br />
strings are to be input.<br />
Debugging scripts<br />
Windows may fail to be activated and screen synchronizations may fail when<br />
the <strong>SilkPerformer</strong> <strong>Citrix</strong> replay encounters different values during replay than<br />
were captured during recording. Sometimes the causes of synchronization<br />
problems are not apparent — they may be due to a change in screen position of<br />
only a single pixel.<br />
More common than screen synchronization failures are windows not being<br />
activated during replay. In such cases the screenshots associated with the<br />
corresponding user actions may explain the fault (sometimes there is no user<br />
fault and a window is activated only sporadically. In such cases you must<br />
remove the associated <strong>Citrix</strong>WaitForWindow function).<br />
<strong>SilkPerformer</strong> <strong>Citrix</strong> replay captures screengrabs when errors occur (the default<br />
setting) and writes these bitmaps to disk. By default the recorder writes<br />
screenshots to the screenshots directory in the project directory. Replay stores<br />
screenshots in the current used result directory. Visual comparison of record and<br />
replay screens can be done best by using bitmap viewing programs.<br />
38 <strong>SilkPerformer</strong> <strong>Citrix</strong> <strong>Tutorial</strong>