Degust works with tests and test steps.
Degust can run thousands of tests in parallel, all running side by side or exchanging information with each other to create an overall picture.
Unlike all known test programs, however, Degust ensures that no competing test steps are started at the same time on a device.
This prevents test results from being contaminated by other tests.
The problem does not even occur if a test consists of many steps and is started alone on a device. In this case, the test steps are executed in order by definition, since they can also depend on each other or build on each other.
It becomes interesting when several tests are started in parallel on one device.
Here it can happen that e.g. different load tests are started.
Exactly here Degust synchronizes the test steps in such a way that never parallel test steps can run, which can cause mutually negative effects.
When designing the tests, the user can decide whether to combine many steps into one test, or to create several tests with fewer or only one step.
The advantage is obvious:
A test with 10 steps, each taking 15 seconds, requires at least 150 seconds to run, plus some overhead for result evaluation and processing.
If the steps could be executed in parallel, it may be useful to split the test into smaller units. Referring to the previous example, the entire test scope can be finished after 15-20 seconds if the user configures 10 tests with one step each.
This sounds like extra work, but the 'Clone' or 'Save as New' function and the template feature of Degust make the tasks easier.