TestCases section (blue)
In Tosca, TestCases in plain English are created in the blue section. A TestCase is defined by a sequence of test commands in the form of TestSteps and TestStepValues. TestStep folders provide an additional way of structuring objects, when necessary.
XTestSteps can be used analogous to classic TestSteps. Classic TestSteps are described in detail in chapter "Create and manage TestCases".
XTestSteps
-
Individual branches of the structure can be deleted.
-
Individual parts can be duplicated.
-
Additional structures can be attached.
Rearranging TestSteps
The option Allow Reorder enables you to modify the order of XTestStepValues in an XTestStep. XTestSteps with reordered XTestStepValues contain the property ReorderAllowed with the value True.
Restoring the default order
The option Set Default Order is available in the context menu for XTestSteps whose XTestStepValues were modified via the option Allow Reorder. This restores the original order of the XTestStepValues.
Synchronizing TestSteps
If the hierarchy of XModuleAttributes is modified, the corresponding XTestStepValues are marked with a warning symbol. The option Synchronize, which is provided in the context menu of the superordinate XTestStep, transfers the modified XModuleAttributes to the XTestStepValues. The XTestStepValue, including its Value and ActionMode, is then moved to the new position and deleted from the old one.
For automated synchronization, the following requirements must be met:
-
the XModuleAttribute to be moved is generated exactly once (as an XTestStepValue).
-
the future parent node must be uniquely identifiable.
Please note that both XML 3.0 and Webservice 3.0 Engine (non-GUI)TestCases cannot be synchronized. |
The context menu entry Create XTestStepValue tree generates all initially created XTestStepValues that are present in this TestStep. The wildcards remain available for further generation processes, depending on the value assigned to the property Cardinality (see chapter "Default properties for Modules").
XTestStepValues
The basic options and properties of XTestStepValues are similar to those of classic TestStepValues.
When an XTestStep is created by dragging & dropping an XModule onto a TestCase, XTestStepValues are either created initially as wildcards or as generated XTestStepValues.
When creating XTestStepValues, please note that many properties can be predefined in the Modules section, such as Cardinality or the property ExplicitName.
ActionModes are used to steer the test object. They define how the value in the Value field should be applied in order to steer the control (see chapter "ActionModes").
Properties
Properties to be verified are entered in the Value column (see chapter "Verifying properties").
For further information, please refer to chapter "Using properties of controls".
DataType |
Description |
---|---|
String |
The exact string is processed, regardless of the ActionMode (default setting). |
Numeric |
The value in the Value field is interpreted as a number. |
Password |
Value inputs into the Value field are displayed with wildcard asterisks [*] in Tosca Commander™. The values are saved encrypted too. |
Boolean |
The DataType has to be set to Boolean for the binary expressions True/False. They are not case-sensitive. |
Date |
The value in the Value field is interpreted as a date. This prevents the use of different date formats from influencing the test. |
Deleting TestStepValue values
Values of a generated TestStepValue can be deleted by clicking on Delete in the context menu or by pressing the Del key.
The value of the TestStepValue can either be deleted manually or via the key combination Ctrl + Del. This applies to the following ActionModes: Select, Constraint and Insert.
If a dynamic expression is used for specifying values, this can be translated indirectly via the context menu option Translate Value (see chapter "Specify values"). The subsequent dialog box shows either the translated value or a note on the fact that the expression can not be translated.
Translating values
Relative paths
TestCase templates in Tosca TBox can use the column Path for relative paths, which is similar to the Path column in Tosca Commander™ (see chapter "Combining TestCase templates with data sources"). If a relative path is entered into the Path column for a TestStepValue, this path is valid for all TestStepValues that are listed beneath.
ScratchBook
In ScratchBook, TestCases can be temporarily arranged and executed upon test case creation. You are able to arrange TestCases, TestSteps or test folders arbitrarily and execute them.
The option Run in ScratchBook can be selected from the context menu of TestCase folders, TestCases and TestSteps.