You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

What is a Pre-Condition


Pre-Conditions specify the conditions that need to be fulfilled in order to execute a test.

 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.  


Test and Pre Cond




Creating a Pre-Condition

To create a new Pre-Condition issue:

Click the Create Issue at the top of the screen to open the Create Issue dialog box.

Step 2: Select the relevant Project and on Issue Type select Pre-Condition.

Step 3: Type a Summary for the Pre-Condition and complete all appropriate fields — at least, the required ones which are marked by an asterisk.

Step 4: On the Pre-Condition Details tab, select the Pre-Condition Type and complete all appropriate fields.


Optional:
- Click on the Tests tab to associate the current issue with Tests.

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 1: Click the Edit button (at the top-left of the 'view issue' page) to open the Edit Issue dialog / page.

Step 2: Modify your Pre-Condition details in the appropriate fields of the Edit Issue General tab.

Step 3: Modify your Pre-Condition's Details under the identically named tab on the Edit Issue page.

Optional:
- Click on the Tests tab to edit Test associations.

Step 4: Click the Update button to save your changes.



Clone


Cloning a Test issue creates a new Test with all the information of the cloned Test, except its executions. Therefore, the cloned issue will not be associated with any Test Execution issue.



Select More > Clone. The Clone Issue screen will appear.



You can edit the clone Test's Summary if you wish.

  - If the test contains links to other issue(s), you can select whether or not to include the links in the new clone test.

  - If the test contains sub-tasks, you can select whether or not to create the sub-tasks in the new clone test.

  - If the test contains attachments, you can select whether or not to include the attachments in the new clone test.

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

Others


Test are Jira issues, that means that you can create Test using CSV , Rest API or any other forms you use today. Check REST API for details on the specifics for Xray REST API






  • No labels