Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

From the requirement issue screen

UI Steps

Using the top "Create" button"

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

Image Removed

Select the  Project  and on  Issue Type,  select Test.

Image Removed

 On the Test Details tab, select the Test Type and complete all appropriate fields;

UI Step
Info

There are 3 Types of Test in Xray they are : Manual , Generic and Cucumber

We will talk on them in the next chapter, for now we will stick with the most common one "Manual"

Select the Test Type as Manual and feel free to add some 
  Image Removed 
UI Step
Info

To proceed as described below your admin as had to configure globally Requirements and Defects and Requirement coverage as been enabled for your project.

If you are not able to see it reach out your Jira admin as this needs to be set up by a Jira administrator.

Go to a requirement in your project (e.g Story) and click "Create new Test" just like highlighted in the picture below.

Image Removed

Select the  Project and on Issue Type make sure you have Test selected.

Image Removed

    And follow the same steps already described above to fully define your test.

Tip
titlePro Tip

The concept as you probably already figure it out is the same as  Epics and Stories.

UI Step

Clone

Info

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.

Image Removed

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.

Image Removed

UI Step

Extra

Creating a Cucumber Test


Info

Cucumber is a tool that executes plain-text functional descriptions as automated tests. The language that Cucumber understands is called Gherkin, which is a business-readable, domain-specific language that describes the software’s behavior without detailing how that behavior is implemented. It is line-oriented language and uses indentation to define structure. Line endings terminate statements (e.g., steps). Either spaces or tabs may be used for indentation (but spaces are more portable). Most lines start with a keyword.

For more information on the Cucumber Basics, please consult the Wiki and Tutorials at: http://cucumber.io


Gherkin Tests are divided in two Scenario Types:

  •  Scenario: a set of instructions exclusively composed of constant values, which, when executed by a tool, will only give a static result (e.g., 2 + 3 = 5)
  •  Scenario Outline: a generic set of instructions containing variables, which, when executed by a tool, will prompt varied results according to the specified input.

The Scenario Types are inferred from the Scenario specification, i.e., the behavior to be reproduced by the Cucumber tool in entered in the Steps field.

Image Added



UI Step

Export to Cucumber

Cucumber Tests in Jira can be exported to feature files ready to be executed in Cucumber. The generated feature files follow the rules defined in Export Cucumber Features and take into account the context of the Jira Test issue.

This action will prompt a FeatureBundle zip file containing a single Cucumber feature file for every Requirement associated with the target Test, to be generated and downloaded. 

To export a Cucumber Test issue to feature files, 

Step 1: Open the Cucumber Test issue view page. 

Step 2: Select ... > Export to Cucumber. The file will be downloaded to the browser.


image2020-5-18_18-30-0.pngImage AddedTest 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