Page History
...
A Pre-Condition is like defining the step "0" for your tests. This is very useful in many use cases where you have to start by doing exactly the same thing. For example, if you are going to do something on a system, you most probably have to authenticate first, right? But sometimes, you have to do several things (e.g., restore DB, authenticate) before going through your Test steps. And each of those things may be done and used independently, i.e., some Tests may require just restoring the DB, another may require just to authentication, and others may require both things or more.
| Table of Contents |
|---|
Pre-Condition Types
Pre-Conditions Types must be the same Type of the Test they are associated with, so they can be Manual or Automated.
- Manual Type Pre-Conditions: Conditions to be executed by the user before starting the Associated Test.
- Automated[Generic] Type Pre-Conditions: Conditions to be executed by the external tool before starting the Associated Test.
- Automated[Cucumber] Type Pre-Conditions: Cucumber Background Gherkin clauses to be executed before starting the associated Scenarios.
Actions
| Table of Contents | ||||
|---|---|---|---|---|
|
Create
To create a new Pre-Condition issue:
...
Step 5: When you are satisfied with the content of your Pre-Condition, click the Create button. If you selected the Create another check box (above), a new Create Issue dialog appears. This issue is automatically pre-populated with your previous Pre-Condition details, while leaving the Summary field blank.
Edit
Using the Edit Issue dialog box
To Edit an existing Pre-Condition issue using the edit page:
...
Step 4: Click the Update button to save your changes.
Using the Inline Edit for Jira App
To Edit an existing Pre-Condition issue using inline edit:
...
Step 2: To save the changes, just click outside of the field area of click the save button located in the bottom right corner of the editing field.
Clone
To clone a Pre-Condition issue:
...
- If the pre-condition contains links to other issue(s), you can select whether or not to include the links in the new clone pre-condition.
- If the pre-condition contains sub-tasks, you can select whether or not to create the sub-tasks in the new clone pre-condition.
- If the pre-condition contains attachments, you can select whether or not to include the attachments in the new clone pre-condition.
Step 4: Click Create.
Change Pre-Condition Type
If the Pre-Condition type is changed, and the Pre-Condition is already associated with tests, a validation process will take place to check if there are any conflicts between Test types and the new Pre-Condition type. If there are conflicts, a confirmation popup dialog will appear showing the Test issue keys with different types. If the operation is confirmed, the association between the Pre-Condition and the conflicted Test issues will be removed.
Screenshot: Example Delete Pre-Condition Association? dialog box
Associate Tests
To associate Tests with a Pre-Condition from the Pre-Condition issue view screen:
...
Step 2: Click the Associate Tests button (under the Tests tab on the view page) to open the Add Tests dialog box.
Step 3: Select or search the Test issues to be associated with the Pre-Condition:
Select Test Issues - In order to select the Tests to be associated you can, under the Select tab:
- Input the desired Test Issue Key on the Tests field
- Click on the Down Arrow on the Tests field and select the Test from its History Search list
- Click on the + button which will prompt an Issue Selector Pop-Up
- Click on the Search tab to use the Find Jira issues browser (more details here)
Search Test Issues - In order to search for Tests to be associated you can, under the Search tab:
- Browse for the desired Test Project, Type or terms it Contains
- Click on the More button to add more browse fields such as Label, Fix Version, Test Set, Test Set Fix Version, Requirement, Requirement Fix Version, Saved Filters and Workflow Status
- Click on the Magnifier button after filling the browse fields to get a list of matching entries
- Click on the Advanced button to perform a JQL search (more details here)
Open the Search tab.
| Info | ||
|---|---|---|
| ||
This is an example of how to add tests, using some of the features available in the Search tab. For more information, please visit the Issue Picker Dialog detailed overview. |
Step 4: Configure the search.
-Use the Filters dropdown button to include extra fields in the search criteria.
-Fill in the filters values.
-Press the search button.
Step 5: Select and Add tests.
- Once the results are obtained you can order, add/remove columns to the results list (the columns selection is saved as a preference).
- Check the tests you wish to add from the listed results.
Step 6: Add tests by pressing "Add selected"Step 4: Click Add.
Remove Tests
To remove Tests from a Pre-Condition using the Pre-Condition issue view screen:
...
Step 2: On the Tests table, hover over the desired Test row and click on the Trash button that appears at the end of the row. You will be prompted with a confirmation dialog.
Bulk Operations
Xray provides the following bulk operations on the Tests table.
...
Step 3: Selected the desired Test issues.
Step 4: Click the bulk actions gear located on the actions column header and the bulk actions button and choose one of the available actions.
