Settings - Synchronization

The following settings are located at Settings->TBox->Synchronization:

Synchronization Timeout
Description	Maximum time to be waited (in milliseconds) until the object to be tested has adopted the expected state. The time to be waited between the attempts is included.
Example	10000

Synchronization Timeout during WaitOn
Description	Maximum time to be waited (in milliseconds) until the object to be tested has adopted the expected state when used along with the ActionMode WaitOn. The time to be waited between the attempts is included.
Example	20000

The settings listed below are located under Settings->TBox->Synchronization->Waiting for Cursor.

These settings allow the status of the mouse pointer to be checked prior to continuing with the test execution. The value of the setting Waiting for Cursor must be set to True in order to enable the following settings.

Busy shapes
Description	Here you can specify which shape the cursor should take if it is busy. Various forms can be specified separated by semicolons. Possible values: AppStarting, Arrow, Cross, Hand, Help, IBeam, Icon, No, Size, SizeAll, SizeNESW, SizeNS, SizeNWSE, SizeWE, UpArrow and Wait.
Example	Wait;AppStarting

Busy shapes

Description

Here you can specify which shape the cursor should take if it is busy. Various forms can be specified separated by semicolons.

Possible values: AppStarting, Arrow, Cross, Hand, Help, IBeam, Icon, No, Size, SizeAll, SizeNESW, SizeNS, SizeNWSE, SizeWE, UpArrow and Wait.

Example

Wait;AppStarting

Cursor idle duration
Description	Defines the time to be waited after the cursor has returned to its original shape. The time is specified in milliseconds.
Example	100

Mouseover offset X-axis
Description	This indicates the distance from the left pane of the window to the cursor in percent. The cursor is set to this position and verified prior to performing an operation. The center of the application window is specified by default.
Example	50

Mouseover offset X-axis

Description

This indicates the distance from the left pane of the window to the cursor in percent. The cursor is set to this position and verified prior to performing an operation.

The center of the application window is specified by default.

Example

Mouseover offset Y-axis
Description	This indicates the distance from the upper pane of the window to the cursor in percent. The cursor is set to this position and verified prior to performing an operation. The center of the application window is specified by default.
Example	50

Mouseover offset Y-axis

Description

This indicates the distance from the upper pane of the window to the cursor in percent. The cursor is set to this position and verified prior to performing an operation.

The center of the application window is specified by default.

Example

Move mouse over application
Description	This setting specifies whether the mouse pointer should hover over the application window prior to checking the cursor's state.
Example	True

Waiting for Cursor
Description	Specifies whether the cursor's state should be checked prior to executing XTestSteps or XTestStepValues. The test execution continues only after the mouse pointer has taken its original shape.
Example	False

Waiting for Cursor

Description

Specifies whether the cursor's state should be checked prior to executing XTestSteps or XTestStepValues.

The test execution continues only after the mouse pointer has taken its original shape.

Example

False

Synchronization settings can be defined for one or more objects by using test configuration parameters or Steering Params. Parameters overwrite the global setting of the Settings dialog.

The parameter name matches the name of the respective setting without any spaces.

If the steering param WaitingForCursor is set on the Module level, this will have no effect on the subordinate ModuleAttributes.

Test configuration parameter WaitingForCursor

Parameter PageSync

In addition to the settings described above, you can also use the parameter PageSync. If you set the value to true (case-insensitive), Tricentis Tosca discontinues test execution until all AJAX requests of the browser have been processed.

This applies to all AJAX requests that are started after Tricentis Tosca has accessed the site. AJAX requests that were started by loading the site are not affected.