Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
CASE 1
How to reproduce:
- set Xray settings, under Test Statuses, final precedence flag to true
- create a story A, associate it with v3.0
- create a Test X linked with the previous story
- from the Test issue screen, create a Test Execution for the Test, for version "v3.0" and assign it to the Test Environments: "Win10", "Windows" . Set the Test Run to "FAIL".
- from the Test issue screen, create a Test Execution for the Test, for version "v3.0" and assign it to the Test Environments: "Linux", "RHEL6" . Leave the Test Run in "TODO".
- from the Test issue screen, create a Test Execution for the Test, for version "v3.0" and assign it to the Test Environments: "Win7", "Windows" . Set the Test Run to "PASS".
- create a Test Plan for version v3.0, add Test X and associate the previous Test Executions
Expected results for the Test status, per environment, on version v3.0:
| Windows | Win7 | Win10 | Linux | RHEL6 | |
|---|---|---|---|---|---|
| calculated status | PASS | PASS | FAIL | TODO | TODO |
| why? | last executed Test Run, based on its start date, on Windows environment was "PASS" | last executed Test Run, based on its start date, on Win7 environment was "PASS" | last executed Test Run, based on its start date, on Win10 environment was "FAIL" | last (and only) Test Run for Linux environment is on TODO | last (and only) Test Run for Linux environment is on TODO |
Obtained results:
- Story issue screen, within the Test Coverage panel: nok (Test shows as FAIL for Windows environment)
- Tests project tab report: ok
- Tests List: nok (Test shows as FAIL for Windows environment)
- Tests Plan issue screen: ok
Notes: the calculated requirement status seems to be ok though.
CASE 2
How to reproduce:
- set Xray settings, under Test Statuses, final precedence flag to false
- create a story A, associate it with v3.0
- create a Test X linked with the previous story
- from the Test issue screen, create a Test Execution TE1 for the Test, for version "v3.0" and assign it to the Test Environments: "Win10", "Windows" . Set the Test Run to "PASS".
- from the Test issue screen, create a Test Execution TE2 for the Test, for version "v3.0" and assign it to the Test Environments: "Linux", "RHEL6" . Leave the Test Run in "TODO".
- from the Test issue screen, create a Test Execution TE3 for the Test, for version "v3.0" and assign it to the Test Environments: "Win7", "Windows" . Set the Test Run to "FAIL".
- in the Test issue screen,
- change inline the result of Test in TE3 from FAIL to PASS
- change inline the result of Test in TE1 from PASS to FAIL
- create a Test Plan for version v3.0, add Test X and associate the previous Test Executions
Expected results for the Test status, per environment, on version v3.0:
| Windows | Win7 | Win10 | Linux | RHEL6 | |
|---|---|---|---|---|---|
| calculated status | PASS | PASS | FAIL | TODO | TODO |
| why? | last created Test Run, based on its created date, on Windows environment was "PASS" | last executed Test Run, based on its created date, on Win7 environment was "PASS" | last created Test Run, based on its created date, on Win10 environment was "FAIL" | last (and only) Test Run for Linux environment is on TODO | last (and only) Test Run for Linux environment is on TODO |
Obtained results:
- Story issue screen, within the Test Coverage panel: nok (Test shows as FAIL for Windows environment)
- Tests project tab report: ok
- Tests List: nok (Test shows as FAIL for Windows environment)
- Tests Plan issue screen: ok
Notes: the calculated requirement status seems to be ok though.
Attachments
Issue Links
- is cloned by
-
-
- Closed
-
