Drive OS-related controls (Windows, Mac, or Linux) as part of your overall system test (for example, triple-play testing, VOIP testing, VPN connection tests, and so on).
* Interact with a remote GUI environment (primarily Windows) using VNC. As a result, you can effectively use administrative tools to configure the remote environment or execute manual test cases within the context of a standard tool.
* Record and review the actions executed in a remote environment through the VNC protocols. As a result, you can have a record of the actions performed during a test or administrative action and can use those as the foundation for future automation.
* Interact with the command shell on a remote Windows environment in such a way that you can apply standard iTest CLI automation technology to the Windows shell (for example response mapping). As a result, you can use a broader range of iTest features and potentially have a greater degree of control than a standard VNC playback may afford.
* Replay actions previously recorded over a VNC session in a robust manner, independent (to the extent possible) of changes in window position, layering, extra windows or controls on the screen, dynamically changing content, and other variations in the user experience. As a result, your replay scripts are robust and automation is repeatable.
