Page History
...
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Note: If you don't use Test Environments, then the TestRunStatus is calculated as usual.
| Info |
|---|
If you start using Test Environments in your Test Executions, then it's not only your test status calculation that will change. All custom fields that depend on it (e.g., Requirement status, Test Sets status) will change. Consequently, the requirement coverage calculation and all associated charts/gadgets are also affected. |
...
| 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 of "TestRunStatus" custom field |
|---|---|---|---|---|---|
A | Android | iOS | PASS | PASS | PASS |
B | iOS | iOS | PASS | FAIL | FAIL |
C | iOS | iOS | FAIL | PASS | FAILPASS |
D | iOS | - | FAIL | PASS | FAIL |
E | - | - | PASS | FAIL | FAIL |
F | - | - | FAIL | PASS | PASS |
Example
When creating a Test Execution, you must set the Test Environment in which the execution will be executed. You can use this field as a simple label: just add the environment or reuse a previously created one.
...
Test Execution for “iOS” Test Environment
The Test Environments column is shown in your Test Runs table so you can distinguish each execution of the Test between the different environments.
The same Test has been executed in both Test Environments (a Test Execution per Test Environment).
The Requirement Status will show NOK because the Test has failed for one of the environments.
...
- Use Test Environments only if want to run the same Test on different environments.
- If you do use it, then assign just one Test Environment per Test Execution.
- You may filter using Test Environments in your Test Executions panel to see how the executions are doing, per environment.
...