Page tree

This is the documentation of Xray Server. If you are looking for Xray Cloud, visit this page. Documentation of older versions of Xray Server is available in this page.

Skip to end of metadata
Go to start of metadata

"Test Environment" is a concept introduced in Xray v2.

Here is a short video which explains Test Environments and how you can use them.

Overview

The status of a Test  (i.e., TestRunStatus) is generally calculated by looking at the Test's last execution (more detail here). However, this does not work well if you execute the same Test in two different test environments (e.g., devices) and you want the two results to be consolidated. 

Within a Test Execution, you may specify the Test Environment(s) where the tests will be executed in the respective attribute. A Test Environment is similar to a label, but Xray has special logic to deal with it.

If you use Test Environments, you may reuse the same Test for multiple test environments and create Test Executions for each one. If you don't use Test Environments and you want to track tests for multiple environments (e.g., devices), then the only way to do it is to create multiple tests, one per each test environment.

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.


test_environments


Note: If you don't use Test Environments, then the TestRunStatus is calculated as usual.


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.

How it works

Let's say we have a Test being executed two times. We will start by creating Test Executions TE1 and TE2.

TE2 will be executed after TE1, so TE1 is considered older.

Below are example scenarios and shows how the TestRunStatus is calculated in each.

If you have a mix of Test Executions (i.e., with and without Test Environment as in scenario D), it wil be treated the same way as scenarios A, B and C.


ScenarioTest Environment(s) of TE 1Test Environment(s) of TE 2Test run status in TE1Test run status in TE2Calculated value of "TestRunStatus" custom field

A

AndroidiOSPASSPASSPASS

B

iOSiOSPASSFAILFAIL

C

iOSiOSFAILPASSPASS

D

iOS-FAILPASSFAIL

E

--PASSFAILFAIL

F

--FAILPASSPASS 


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 “Android” Test Environment

 

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.

 


Tips

  • 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.

Learn more

For advanced Test Environment management capabilities, please check our Integration with Apwide Golive.




  • No labels