You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the metric named 'test cases' Jira is being used as a source for test cases.
JUnit, TestNG, and Robot Framework are supported as source for the test results.
test cases (Jira)
test results (JUnit)
test case 1
test result 1: passed
test case 2
test result 2: failed
test case 3
test result 3: skipped
NULL
test result 4:passed
test case 5
test result 5: untested
test case 6
test result 6: errored
test case 7
test result 7
The above table could be a realistic scenario. It would be great if the user can control what he/she can see and that he understands how this metric comes to the resulting measurement, in other words in which direction deduplication works.
I would like to be able to configure:
all test cases that have no test result
all test results that have no corresponding test case (orphans)
and of course filter on all possible statuses
PS: errored is not a grammatically correct verb in English. Please use 'generated error', or just 'error'.
The text was updated successfully, but these errors were encountered:
For the metric named 'test cases' Jira is being used as a source for test cases.
JUnit, TestNG, and Robot Framework are supported as source for the test results.
The above table could be a realistic scenario. It would be great if the user can control what he/she can see and that he understands how this metric comes to the resulting measurement, in other words in which direction deduplication works.
I would like to be able to configure:
PS: errored is not a grammatically correct verb in English. Please use 'generated error', or just 'error'.
The text was updated successfully, but these errors were encountered: