Page History

...

The following endpoint is provided to import a Cucumber .feature file or a zip file containing multiple .feature files. The files in the zip file may be in folders/subfolders.

In addition to the .feature or a zip file the endpoint also accepts a JSON file which can specify additional information that will be added to the Test or Precondition at the moment of their creation. The format of JSON where additional information for the Test and Precondition can be specified is similar to the one Jira uses to create/update issues, for more information about the format, check the Jira documentation here.

...

Each .feature file will be processed and will try to find or create a Test/Pre-Condition inside the project given in the projectKey parameter. We use the following rules:

Tests:

1. If Test key is present in the file:
   1. exists in Jira, system tries
   try
   1. to find the Test by key
   , if present then
   1. and update it; else...
   2. does not exists in Jira, system returns an error message.
2. If Test key is not present in the file, system tries try to find the Test having:
   1. the same source and original relative path of .feature (e.g. "[project_lambda]core/sample_addition.feature) and
      1. same ID (extracted from a scenario label named id:xxx) or
      2. same summary; else...
   2. the same summary in the target project; else...
   3. create Test in that project. The tags used in the scenario/scenario outline are also added as labels.

Pre-Conditions:

1. If Pre-Condition is present in the file:
   1. exists in Jira, system tries
   try
   1. to find the Pre-Condition by key
   , if present then
   1. and update it; else..
   .
   1. .
   2. does not exist in Jira, system returns an error message.
2. If Pre-Condition key is not present in the file, system tries try to find the Pre-Condition having:
   1. the same source and original relative path of .feature (e.g. "[project_lambda]core/sample_addition.feature); else...
   2. the same summary in the target project; else...
   3. create Pre-Condition in that project. The tags used in the background are also added as labels.

The mapping from the Scenario/Scenario Outline present in the .feature files to the Test issues in Jira would be as follows:

...

@REQ_CALC-889
Feature: As a user, I can calculate the sum of 2 numbers     
       
	Background:
		#@PRECOND_TX-114
		Given that the calculator is turned on
		And the mode is to advanced
		#@PRECOND-_TX-155
		Given that the calculator has been reset

	@UI @core
	Scenario Outline: Cucumber Test As a user, I can calculate the sum of 2 numbers
		Given I have entered <input_1> into the calculator
		And I have entered <input_2> into the calculator
		When I press <button>
		Then the result should be <output> on the screen
	
		  Examples:
		    | input_1 | input_2 | button | output |
		    | 20      | 30      | add    | 50     |
		    | 2       | 5       | add    | 7      |
		    | 0       | 40      | add    | 40     | 
		    | 4       | 50      | add    | 54     |

...

{
    "errors": [
		"Error in file calculator.feature: Precondition with key DEMO-54321 was not found!"
	],
    "updatedOrCreatedTests": [
        {
            "id": "32495",
            "key": "DEMO-15119",
            "self": "https://devxray3.atlassian.net/rest/api/2/issue/32495"
        },
        {
            "id": "32493",
            "key": "DEMO-15117",
            "self": "https://devxray3.atlassian.net/rest/api/2/issue/32493"
        }
    ],
    "updatedOrCreatedPreconditions": [
		{
            "id": "12345",
            "key": "DEMO-12345",
            "self": "https://devxray3.atlassian.net/rest/api/2/issue/12345"
        }
	]
}