Steps for Integrating eG with CitraTest

The primary steps involved in the eG-CitraTest integration are installing the CitraTest Development environment and building a script file using it. To ensure a smooth and effective integration, CitraTest v5.0 or v6.06 needs to be installed. For downloading the CitraTest installable, refer to the URL:, For an elaborate installation procedure for CitraTest, refer to the CitraTest manuals.


Since CitraTest emulates real user transactions by opening client applications and emulating user clicks on the client application, CitraTest requires complete control of the desktop of the system on which it executes. Therefore, CitraTest should be installed on a dedicated system.

The key prerequisites for installation include:

Software Prerequisites:

  • Windows NT or Windows 2000 or Windows XP server/workstation
  • Microsoft Internet Explorer (IE) version 5.0 or higher
  • Microsoft Visual Basic 6.0 (This is required only for installing and using the CitraTest development environment. For the CitraTest Runtime environment though, the VB runtime files that are bundled with the Windows operating system will suffice; in such a case, Microsoft VB is not required).


  • Screensavers should be disabled on the system executing CitraTest
  • Use the LockMachine.exe available in the <citratest_install_dir> to disable the keyboard and mouse of the workstation on which CitraTest is executing. For more details pertaining to the LockMachine utility, refer to the CitraTest Manuals.

Once the development environment is installed, proceed to record a test script. A test script is a sequence of actions that are recorded as a user accesses one of the services in the target infrastructure. The recorded script can then be played back to emulate user accesses to the service. Image and text recognition techniques are used during playback to determine whether playback of a script succeeded or not.

After building the script file, use the eG administrative interface to configure the script playback. Next, start the external agent which will playback the script, and finally, view the measures returned by CitraTest in the eG monitor interface.


If CitraTest is installed and the script created on a remote host using a normal Remote Desktop session, then the eGurkhaAgent service will not be able to execute the CitraTest script due to lack of the requisite permissions. On the contrary, if all the above-mentioned processes had been implemented using the '/console session' of the Remote Desktop, then the eGurkhaAgent service will execute the script and report measures to the eG manager.

The sections to come will take the help of two illustrated examples to explain how eG client emulation works. While the first example deals with a web application, the second example targets a Citrix application.