Although the best practice is to always maintain a 1:1 traceability relation between requirements and test cases, the reality is that, on several ocassions, we're forced to cover more than one requirement with a test case (due to time or resources restrictions on complex/long executions where you can take advantage of a single execution flow in order to verify several requirements). This is not possible in the case of robot framework to Jira plugin, where only the first tag that matches a JIRA Xray requirement key will be linked to the test instead of linking all the included tags that match a requirement key.
The following is an example of a Robot test case where only the first tag QPTM-113 will be linked as the requirement covered for the test, while the QPTM-116 and QPTM-115 will be ignored:
*** Test Cases ***
My dummy test
[Tags] smoke QPTM-113 QPTM-116 QPTM-115
Given My Given Statement Is Fulfilled
When My When Statement Is Executed
Then My Then Condition Is Verified
[Teardown] My Teardown
The possibility to have a 1:N relation between requirements and test cases is something available on the vast majority of test management tools and something that IMO can only add value and more flexibility to the Xray connector.
Feature Request
Although the best practice is to always maintain a 1:1 traceability relation between requirements and test cases, the reality is that, on several ocassions, we're forced to cover more than one requirement with a test case (due to time or resources restrictions on complex/long executions where you can take advantage of a single execution flow in order to verify several requirements). This is not possible in the case of robot framework to Jira plugin, where only the first tag that matches a JIRA Xray requirement key will be linked to the test instead of linking all the included tags that match a requirement key.
The following is an example of a Robot test case where only the first tag
QPTM-113
will be linked as the requirement covered for the test, while theQPTM-116
andQPTM-115
will be ignored:The possibility to have a 1:N relation between requirements and test cases is something available on the vast majority of test management tools and something that IMO can only add value and more flexibility to the Xray connector.