Test Execution Environment refers to a collection of one or more machines which are used for running tests. Each such environment has a master node which delegates the test execution responsibilities to the members of the group. For an automation developer, a given machine will act both as the master hub and the node.
In accelQ you can setup multiple Test Execution environments which could cater to different testing requirements. Following environment types are supported:
- On-premise lab: Test execution machines are setup in your premises as an automation farm or lab.
- Saucelabs: If your organization has a subscription with Saucelabs for browser infrastructure, you can configure it here and use for accelQ test runs.
- Browserstack: Similar to the above, if you have subscription with BrowserStack, it can be configured for accelQ test runs.
A tester can also configure her own machine as an execution host, which can be used in private mode for running tests. A Project Admin can setup a shared execution environment (typically an automation lab), which can be used by all the users in the project.
To configure or edit a Test Execution environment
- Click on the "Configure" icon in the top toolbar. In the configuration screen, click on "Test Execution Environment" link.
- Click on the "+" icon to create a new test execution environment.
- Provide a meaningful name for the execution host.
- Provide hostname or IP where the selenium grid is running.
- Note: Do not include "http://" prefix in the host name.
- Note: In case you are using ngrok for Agent access, Host Name should be the forwarding address you get from ngrok configuration. Click here for details.
- Provide port number to access Selenium grid. This port is 4444 in case you have direct access to accelQ agent or port 80 if you are using ngrok as a secure tunnel.