Page History
...
Let's say that you have executions for two Test Environments: "Android" and "iOS". The test is considered as PASS only if the latest executions for Android and iOS are both PASS; otherwise, it will be FAIL.
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Note: If you don't use Test Environments, then only the latest result matters for assessing the current status of the Test.
...
If you have a mix of Test Executions (i.e., with and without Test Environment as in scenario D), it will be treated the same way as scenarios A, B, and C.
| Scenario | Test Environment(s) of TE 1 | Test Environment(s) of TE 2 | Test run status in TE1 | Test run status in TE2 | Calculated value for the overall, consolidated status of the Test (i.e. for the "All Environments") | Other |
|---|---|---|---|---|---|---|
A | Android | iOS | PASS | PASS | PASS | The test will be considered to be PASS in both Android and iOS environments. |
B | iOS | iOS | PASS | FAIL | FAIL | The test will be considered to be FAIL in iOS. |
C | iOS | iOS | FAIL | PASS | PASS | The test will be considered to be PASS in iOS. |
D | iOS | - | FAIL | PASS | FAIL | The test will be considered to be FAIL in iOS and PASS for the empty environment. |
E | - | - | PASS | FAIL | FAIL | The test will be considered to be FAIL for the empty environment. |
F | - | - | FAIL | PASS | PASS | The test will be considered to be PASS for the empty environment. |
...
It is also possible to analyze testing thoroughly considering Test Environments; this analysis can be done using the Requirement Traceability Report or the Overall Coverage Report, among others.
...