Use TestSteps
A TestCase is a sequence of actions that you want to perform on your system under test (see chapter "Get to know Tricentis Tosca").
These actions are called TestSteps. Each TestStep is an automated task that you would otherwise do manually.
Create TestSteps
You can create TestSteps in the following ways:
-
Drag and drop a Module onto your TestCase as described in chapter "Create TestSteps from Modules".
-
With the Fuzzy Search as described in chapter "Create TestSteps with Fuzzy Search".
-
By converting existing TestCases into TestSteps as described in chapter "Convert TestCases into TestSteps".
This section of the documentation deals with automated TestCases.
For information on how to create and design manual TestCases, see chapter "Working with manual TestCases".
Icon |
Description |
---|---|
|
TestStep folder |
|
TestStep |
|
XTestStep |
TestStep properties
DefaultOrderChanged
The order of the TestStepValues within a TestStep can be arbitrarily changed. If this order does not correspond to the ModuleAttributes order of the corresponding Module, this TestStep will be marked with DefaultOrderChanged=True.
The original order of the Module can be restored by using the option Set Default Order.
OutOfSync
Shows whether the synchronization is to be performed with an associated TestStepReference (part of a TestStepLibrary).
IsPausable
This property shows the value which has been determined for Pausable. If Pausable is set to either True or False, then IsPausable also receives the same value. If the property Pausable is set to Inherited, the value of the superior object is copied. An explicit value in a subordinate object always overwrites the value of the superordinate object.
Specifies whether the TestStep can be paused (see chapter "Execute manual tests"). This property can only be edited with manual TestSteps. The value of this property is False for all the other TestSteps and can thus not be edited. This value is always False in TestStepLibraries.
Options for TestSteps
Reset values
All values and settings of the TestStep are reset to the default settings.
Allow Reorder
The option to change the order of TestStepValues is enabled with Allow Reorder.
TestSteps and TestCase folders can be disabled. Any TestSteps that are contained in such a folder are also disabled. Disabled objects will be skipped during the execution.
If the option Disable is selected, the following dialog window opens: Disable reason. The reason for disabling can be specified in a free text field. It will later be displayed as a tooltip of the respective object under the property DisabledDescription.
Enable
Objects can be reenabled by selecting Enable from the context menu.
If the hierarchy of XModuleAttributes is modified, the corresponding XTestStepValues are marked with a warning symbol. The context menu entry Synchronize copies the modified XModuleAttributes to the XTestStepValues. The XTestStepValue including its Value and ActionMode entries are then moved to the new position and removed from the old one.
The automated synchronization requires that
-
the XModuleAttribute to be moved is generated exactly once (as an XTestStepValue).
-
the future parent node is to be clearly determined.
Set Default Order
The order of the TestStepValues is changed according to the arrangement of the ModuleAttributes in the corresponding Module.
Snap
All values of a TestStep are set to the values provided in the application.
Run in ScratchBook
Executes one or more selected TestSteps in ScratchBook.
Create XTestStepValue tree
This option allows any initially created XTestStepValues, which exist in this TestStep, to be generated. The wildcards remain available for further generation processes, depending on the value assigned to the property Cardinality (see chapter "Default properties for Modules").
Deleting TestSteps
When selected, TestSteps can be deleted by simply clicking on Delete in the context menu or the dynamic menu TestCases, or by pressing the Del key.