Versions Compared

Key

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

...

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..
    .
    1. .
    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:
      try
      1. exists in Jira, system tries to find the Pre-Condition by key
      , if present then
      1. and update it; else...
      .
      1. does not exist in Jira, system returns an error message.
    1. 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:

    ...

    Code Block
    @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     |

    ...