Xscan in tosca12/14/2023 ![]() XModules: Tosca XScan identifies the values while scanning the control types ComboBox and ListBox and automatically adds them to the Module.Īlternatively, you can specify the values manually. The ValueRange in the Details tab contains a list of values that are separated by semicolons.Ĭlassic Modules: You can specify these values manually.Īlternatively, Tosca Wizard identifies them while scanning the test object and automatically adds them to the Module. This property is only shown in the Details tab ( see "ValueRange"). Specifies the user group for whom an object is visible ( see chapter " Specifies the Tricentis Tosca version used to scan the Module. Use this parameter to define a technology-specific property.Ĭontains the object's unique identification number in the workspace. Possible values: CannotBeExecuted, CustomizableDefaultIsOn ( see chapter "Synchronization - enable/disable"). This modifies the SynchronizationPolicy of the selected object. This does not have any impact on automated control steering. A control type ( BusinessType) must be specified as a value for this property. Use it to assign the icon of a ModuleAttribute to a specific control type. The revision number increases whenever an object is checked in or out. The value of this property is automatically assigned in multi-user environments. Specifies the user group that is authorized to modify objects ( see chapter " Indicates the TOSCA user name of the user who last modified the object.Ĭontains the unique path to the object in the workspace. Indicates the date and time when the object was last modified. Indicates whether a Module is a TBox Module ( True) or not ( False). Indicates whether the current user has checked this object out ( True) or not. Abstract Modules cannot be used in the TestCase ( see chapter "Generalizations and Specializations"). Indicates whether your Module is abstract or not. Implicit (XModuleAttribute): The InterfaceType of the parent object is used (default value). ![]() ![]() NonGUI: All available ActionModes are visible. GUI: The number of ActionModes provided is limited to those required for graphical user interfaces ( see "TestStep Values, Using XTestStep Values"). Specifies whether the test object is a GUI or nonGUI. Indicates the technology used for steering the test object (e.g. The information that is stored here does not have any impact on automated control steering. You can write any information to this text field. This value is then inherited to specializations and module references ( see chapter "Structure XModules"). The DataType defined on the ModuleAttribute level is applied to the TestStepValues, but it is not binding.ĭefines a default value which is automatically copied to the TestCase whenever the XModule is used. The DataType indicates the type of entry that is specified in the TestStepValue's Value field. Some controls receive a default value when you scan them with Tosca XScan.ĭefines the DataType's default value for the TestStepValue ( String, Numeric etc.). You can select the available ActionModes from a drop-down list, depending on the specified Interface Type. Newly created XTestStepValues automatically receive the value specified here if the cardinality of the attribute has a value >0 ( see "Cardinality"). Specifies the default ActionMode for XTestStepValues. Indicates the TOSCA user name of the user who created the object. Indicates the date and time when the object was created. At least one XTestStepValue must be generated. Any number of XTestStepValues may be created.ġ-N: An XTestStepValue is initially created as a wildcard for each XModuleAttribute. The default ActionMode is the value set in the ActionMode column.Ġ-N: An XTestStepValue is initially created as a wildcard for each XModuleAttribute. Only one XTestStepValue may be created.ġ: Exactly one XTestStepValue is created for an XModuleAttribute. Specifies how often an XModuleAttribute may be used as an XTestStepValue in one and the same XTestStep ( see "Using XModuleAttributes repeatedly in the TestCase").Ġ-1: An XTestStepValue is initially created as a wildcard for each XModuleAttribute. each EditBox control has the property Text. Equal BusinessTypes have the same properties, e.g. Starting from the XModuleAttribute this indicates the control type of an attribute, independent of the technology used. On the XModule level this indicates the technology-specific root element, e.g. ![]() To expand it, click on the Properties button on the right side of your window. If you open a new Modules window, the properties pane is collapsed by default. Tricentis Tosca adds some property values automatically upon scanning.Įdit your Module properties in the Properties pane on the right side of your window. Modules and ModuleAttributes have default properties which are automatically created whenever a Module or ModuleAttribute is newly created. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |