Test Environments
The Test Environments tab allows you to manage the test environments against which you would like to start designing your software model and test cases. All images required for your tests will also be taken on the selected environment.
Depending on the type of software you are planning to automate, you will require different test environments. The test environment will contain the Subject Under Test (SUT). Below are a few possible configurations for Test Environments.
The most common scenario is that you setup a dedicated Virtual Machine on your machine locally using Hyper-V, within your infrastructure or in the cloud.
In case your IT department can setup an environment for you, link them these steps to configure the VM with the recommended settings.
To setup a local Virtual Machine select the 
Icon in the top right of the Test Environments window. The used Windows 11 is provided by Microsoft for evaluation purposes. By using the virtual machines, you are accepting the EULAs.
Hyper-V System Requirements:
- 64-bit version of Windows Pro, Enterprise, and Education (Home Versions are not supported)
- Minimum of 4 GB memory
- 60 GB disk space
- Depending on your Hardware - Virtualization may need to be enabled in the BIOS (for example for Lenovo Notebooks)
Click the Icon to start the Wizard
The Wizard will setup a Hyper-V Windows 11 sandbox for you.
After the wizard is completed, a direct connection to your virtual machine will open in a new window. You can always find your Virtual Machine in the Hyper-V Manager. Double click the SandboxWin11 to connect to it.
After connecting to the Virtual Machine run the "ConfigureVm.exe" located on the C: drive. This will setup TightVNC on the Virtual Machine so you can connect your Visual Studio directly to it. You can also download the .exe here.
After you have executed the .exe the Virual Machine will restart.
Give it a moment to restart. After that connect to it by double clicking the "Hyper V Virtual Machine" in the Test Environments list.
The TestResults.io designer supports the following protocols which will allow you to connect to the test machine:
Protocol | Connection | Description |
VNC | Remote | The target test env. requires a VNC server installed on it. |
RDP | Remote | The target test env. needs to have the Remote Desktop Protocol enabled. |
Android | Local | The Android device must have the Developer Options and USB debugging option enabled. |
iOS | Local | Contact us for details on how to setup access to iOS. |
To connect to a Test Environment follow the steps below
- Select the Add VNC button or any of the other available protocols from the split button in the taskbar of the test environments tool window.
- Enter the following details of the test environment:
- Environment Name - a name which will allow you to easily identify the test environment
- Target system - the network IP or DNS name of the test environment
- Username - user name for the test environment (only required for RDP)
- Password - VNC password or user password (for RDP) of the test environment
- RemoteDirectory - optional connection string for the remote directory containing supporting files, installation files and artifacts for your test case execution e.g. to store files from the test case
Please keep in mind that for the VNC connection the target test environment needs to have the VNC server running in order for the env. to work with the TestResults.io designer.
- Confirm the entry by pressing the Add button
- Your test environment will be present in the list of available test environments
In order to connect to your test environment simply double click on the desired environment.
Once the connection with the test environment is established a new window showing the test environment will be shown. This windows is the Remote Viewer window and has several options to interact with the SUT. It will allow you to control your SUT as well as define screens in your software models and take images which can be used by the automation.
With the dropdown in the taskbar of the environments window, you can select an environment as execution environment. That means that when you start a test case execution from Visual Studio, the test case will run on this test environment.
When you connect to an environment it will automatically be set as the execution environment.
To modify or remove a Test Environment simply right click on the Environment name and select the desired action.
You will be navigated to the modification page where you can change the desired parameters. To confirm the changes press the Save button. To cancel any changes click the back button.
There will not be an additional confirmation displayed upon pressing the Delete button.
Instead of connecting to a remote Test Environment you may choose to work on a static image (e.g. a screenshot of the SUT). In order to work with such an image you will need to configure a Static Image Test Environment. To do so, select the Add Static Image button from the split button in the taskbar of the test environments tool window.
After naming the environment, you can chose between two modes in which you can enter the path to the image which will be used as your test environment:
Enter a path in the Static Image Path textbox or click the browse button (highlighted in blue below) and select the desired image file in the Windows Explorer. Confirm your change by pressing the Save button
You can also enable the option of always displaying a dialog when you start test exeuction where you can change the path to the static image. To do so just switch the Open Image path dialog before execution option to On
Dialog to select the static image path when starting a new execution
The format of the remote directory connection string is as follows:
"{\\computername\sharename}"::{username}::{password}
For a azure file share, this could look for example like this:
"\\mystorageaccount.file.core.windows.net\myfileshare"::AZURE\mystorageaccount::ctzMq410TV3wS7upTBcunJTDLEJwMAZuFPfr0mrrA08==This remote directory connection string will be used by the
SystemHelpers.SetUpRemoteDirectory method to map this remote directory on the SUT. You can also map the remote directory on your local PC with the BaseModelHelpers.MapRemoteDirectoryOnHost to make it available to the test case.Last modified 3mo ago