What are the limitations on text or screens verification in Citrix projects in SilkPerformer?
With Citrix scripts, it is possible to add verifications for text or screens via the replay .xlg file in Truelog Explorer. This is discussed in Can verification be done on content in a Citrix environment? and in the TrueLog Explorer User Guide.
However, there are limitations, namely that the verification of text and screens is restricted to those API calls which are part of the "CitrixWaitForXXX" function family (see SilkPerformer"s Help for a full listing of these functions).
It is therefore not possible to verify text on, for example, CitrixUserInput or CitrixMouseClick API calls.
This is as designed, and is due to the nature of the application behaviour. At user interaction events (such as CitrixKeyString), the screen may not be stable... the screen or text which you have viewed in the TrueLog Explorer may disappear a fraction of a second later, and it is therefore not suitable for verification.
In contrast, the CitrixWaitForXXX functions are synchronization functions, and hence suited to verification.