Share this page
When testing a terminal emulator application, many factors affect its speed of operation and therefore can potentially interfere with the run session. For example, host response time can vary depending on the system load.
Synchronizing your run session helps to ensure that UFT One performs the next step in the test or business component only when your terminal emulator application is ready to continue. This prevents incidental differences in host response time and other factors from affecting successive run sessions.
The options for adding synchronization to a test of your terminal emulator application differ depending on the type:
|
Emulator type |
Synchronization options |
|---|---|
|
All emulator types |
You can instruct UFT One to delay the run session:
|
|
Emulators that fully support HLLAPI |
You can synchronize the run session with the response time of the host. By default, during a record session, UFT One automatically generates a Sync statement for the TeScreen object each time the emulator waits for a response from the host. |
|
Emulators that do not support HLLAPI |
When you record using a terminal emulator that does not support HLLAPI, or that has been configured as supporting text-only HLLAPI operations, UFT One automatically generates a Sync statement for the TeTextScreen object each time a specified key is pressed. The default is the ENTER key. UFT One waits a specified period of time, to allow the host sufficient response time. |
