The Test Environments tab allows you to enter the test environments against which you would like to start designing your test model and test cases. In principal these environments should match to the ones configured in the TestResults.io portal. 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 a different test environment. The test environment will contain the Subject Under Test (SUT).
The most common scenario is that you will need a dedicated Virtual Machine within your infrastructure or in the cloud. That means that before designing your first software model/test case you will need to organize yourself a test env. If you don't have access to one, contact your IT department to set one up. The TestResults.io designer supports the following protocols which will allow you to connect to the test machine:
The target test env. requires a VNC server installed on it.
We recommend TightVNC server.
The target test env. needs to have the Remote Desktop Protocol enabled.
The Android device must have the Developer Options and USB debugging option enabled.
To add a new Test Environment follow the steps below
Select the Add new Environment in the bottom of the tab
Enter the following details of the test environment:
Env. Name - a name which will allow you to easily identify the test environment
Env. IP or DNS name - the network IP or DNS name of the test environment
Username - user name for the test environment (not required for VNC)
Password - VNC or user password for 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
Protocol - protocol used to connect to the target environment e.g. RDP/VNC/Android. If left empty, VNC is assumed.
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 will be established a new window showing the test environment will be shown. This windows is the Remote Viewer window and has several options which are described in detail in chapter Interacting with the SUT. Basically it will allow you to interact with the SUT as well as take the desired pictures of the SUT.
To modify the Test Environment simply click on the arrow next to the Environment name.
You will be navigated to the modification page where you can change the desired parameters. To confirm the changes press the Modify button.
In order to remove the Test Environment just press the Remove button in the bottom of the tab.
Instead of connection to a Test Environment you may choose to work on a static image (screenshot of the SUT). In order to work with such an image you will need to configure the Static Image Test Environment. To do so, select the modify button next to the Static Image 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:
Select the Static Image Path button and select the desired file in the Windows Explorer. Confirm your change by pressing the Modify button
You can enable the option of always displaying a notification pop-up where you will set the test env. path once you execute a test case. To do so just switch the Open Image path pop-up before execution option to On
The next time you will start your test case you will prompted with the following pop-up where you will be able to select the path to the image used for the test environment.
The format of the remote directory connection string is as follows:
For a azure file share, this could look for example like this:
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.