Test Step Icons
A Test Case has a number of icons in the top-right corner:
Note that icons will be greyed out if they are not relevant.
Use the following links to navigate to the relevant section:
Clicking the icon will add an Expected Exception section to the Test Step. This should be used when an Exception (Stacktrace or Error) is expected to be thrown by the application and this should result in the Test Step passing.
Once Expected Exception is added, the different operators can be used to capture the Exception and make the Test Step successful. If the anticipated Exception is not thrown, the Test Step will be failed.
This should not be confused with Asserting Error Text being displayed on a screen during UI testing, which is part of functional testing. Refer to UI Assert for more information.
The second icon is to add a Tag or SLA Requirement to the Test Step:
Once a Tag or SLA is associated with a Test Step, reports can be generated with results grouped by Tag, e.g. CRM:
Before this can be used, Tags and SLAs must first be created in Test Settings. Refer to Tags & SLA for more information.
icon will add a Result Assertion
to a Test Step:
Certain Test Steps will create these for you automatically, but they can be added manually as well. Multiple Result Assertions can be added per Test Step.
Parameter Value Source
Parameter Value Source is used to populate a given variable from data stored in Excel or a database. Once populated, this variable is available for use in Test Parameters.
Refer to Read Data From Excel for more information.
The Configure Parameters
) icon allows you to amend the fields associated with a Test Step. Once selected, a dialog box of fields will appear to select from. This is commonly used when adding an API Test Step
via the Org Browser.