This parameter can be used to keep the system from checking if a Siebel page is busy. This parameter can be used to specify a time lag where individual characters of a keyboard command are sent. This function is for instance used if the header of a page overlaps the control to be steered. Setting it to IgnoreSpans improves the table loading performance of the engine.ĭefault value = Default for all other engines.Īllows you to define where the control should be positioned on the screen in order to steer it. This parameter can be defined on a Table ModuleAttribute level. Invisible table contents are included by default upon scanning or table steering, but they will be ignored if the value of this parameter is set to True. Specifies the row to be used for searching the column name ( see 'Defining headers'). if one of the controls in the browsers toolbar has the focus.ĭefines the column where the system searches for the row name ( see 'Defining headers'). This parameter can be used if the currently loaded page should be focused after activating the browser window, e.g. This parameter can be defined on the Module level for steering Microsoft Edge with the XBrowser Engine 3.0. Setting it to False disables that a window will automatically be brought to the foreground, while running a test execution. This parameter can be defined on the Module level. Steering parameters are used to specify the behavior while a control is being steered. Value for HTML input elements, InnerText for all HTML elements, Encoding for an XML declaration, etc. As a prerequisite, the respective technology will need to properly support the reflected object access.Ī search or identification with Reflected IDs is generally slower because far more information from the target processes must be processed.Īs regards the XBrowser Engine, the use of reflected IDs can reduce the functionality of the XBrowser because the object model of various browser vendors is implemented differently.Ī Technical ID is a property that Tosca provides for technology-specific controls. Properties of test objects not included in the default control units of Tosca can be retrieved from the target technology via Reflection. These are the same for all technologies to be steered.Įach button has the property Label, and each TextBox the property Text. You can combine any number of parameters by using AND- links.īusiness IDs are properties which can be used with specific control types.

Identification parameters determine which properties are used to search for the control to be steered. The configuration param Transition including the value XPathToXmlElement is used along with the transition param XPath. The value is the name of the transition to be used for steering. The property of a test object is directly used as the context when searching for an object.Ī transition between technologies or contexts allows various XEngines to be used within the same TestStep.

Specific parameter for the search algorithm in the selected context. You can perform specific tasks with this parameter, for instance, opening xml files ( see chapter 'Embed SpecialExecutionTasks (XModule)'). Indicates whether a Module is a TBox Module or not. Use this parameter for Mobile Engine 3.0 Modules that you created with Image-Based Test Automation ( see chapter 'Image-based test automation for mobile applications'). (This corresponds to the assembly tag ExtensionId) The steering routines of the respective library are used. These values can be selected in the corresponding XTestStepValue.Īn extension ID can be specified as a value of this parameter. Instead of using True, you can also specify several values, separated from each other by semicolons. If the value of this property is true, you can edit the name of the referenced XTestStepValue. This param is available for the TBox DB Expert Module in the context of Tosca BI only ( see chapter 'Run Tosca BI tests in parallel').īy default, XTestStepValue names cannot be changed. If set to True, the Module can be executed with a parallel agent. Specifies the index to be used to identify the control uniquely upon test execution ( see chapter 'Identify by Index'). The parameter is automatically created upon scanning with Tosca XScan. This contains the steering information required for the automation layer in Tosca. Target objects are searched in context and in accordance with the logic of an algorithmic search query.

Specific parameter used for the search algorithm in the selected context. This specifies whether Modules and ModuleAttributes are excluded from being recorded by the Doku Snapper ( see chapter 'Document the execution of your tests'). This parameter defines which TBox components are used for steering controls. Alternatively, you can left-click on the XModule or XModuleAttribute and select the param via Create Object in the dynamic menu Modules.

Xscan in tosca