System Architecture
Gives you an overview of the different components of the TestResults.io platform and their connections.
Last updated
Gives you an overview of the different components of the TestResults.io platform and their connections.
Last updated
The subject under test describes what to test, e.g. your desktop application, your app, your website. The Subject Under Test can either be available isolated, which means it needs to be installed on the test environment, or the Subject Under Test can already be part of a test environment.
The Subject Under Test is provided by you in terms of a web link, an installer, an APK file or an instruction on how to install your Subject Under Test on the applicable test environments.
We refer to the Subject Under Test as "SUT".
A test environment describes where to test, e.g. on a fresh Windows installation, an Apple iPhone, a set of Samsung Galaxies or a dedicated local environment.
Usually a test environment is independent of the SUT. Therefore, TestResults.io provides you the option to have a dedicated installation process for your SUT for any selected test environment. The test environment itself gets automated in exactly the same way your SUT is automated.
TestResults.io provides you some default Test Environments like Windows, Ubuntu, etc.
We refer to the Test Environment as "ENVIRONMENT".
The test designer is used to tell TestResults.io how to test. This is where the test automation engineer automates all test cases. Within the test designer your SUT is already running in a target ENVIRONMENT and the automation engineer can define screens, their content, their interactions and their expected results.
An execution is a combination of a SUT and an ENVIRONMENT and one or more automated tests to run against this combination. In addition, the execution also links the created test results and optionally collected test artifacts.
Our Test Scaler is one of the unique parts in TestResults.io. It is in charge to make sure that all executions are executed as fast as possible. In fact, if the setup allows it, it will make sure that it can spin up a new ENVIRONMENT for every single test case in parallel.
In addition the test scaler is also in charge that you can run any existing test also as performance/load or stability/monitoring test.
In case you are connecting to on-site ENVIRONMENTs the scaler is aware of all available resources and makes sure they are utilized the best.
Project Hosting refers to the part the you use to control all your projects, test cases, test reports, executions, SUTs, ENVIRONMENTs and additional statistics. In general this is the backend of the TestResults.io test platform. You can access project hosting either via our modern, available everywhere web portal or by integrating our backend into your continous integration pipeline via a simple but powerful REST API.
While the TestResults.io platform supports multiple test engines the suggested primary engine for end-to-end testing is the TestResults.io Visual Testing Engine. This engine allows you to test the Subject Under Test as if a human would verify your software.
Based on image and super advanced, biased character recognition the TestResults.io Visual Testing Engine enables you to define your test cases and test models in a fraction of the time that it usually takes to create a maintainable test model.
