Test automation for complex and distributed systems

Automate test execution across devices, machines and environments without losing the context behind each run.

TS Factory coordinates distributed scenarios, records the test environment and centralizes results. Midair connects those runs with code findings and runtime evidence.

Running a test automatically is the easy part.

The difficult part begins when one scenario depends on several machines, devices, configurations or services.

Automation becomes fragile when the test can run again but the environment behind the result cannot be reconstructed.

Tests depend on infrastructure

A scenario may require several hosts, devices, services or network conditions to be prepared before execution.

Environments drift

Configuration changes between runs can make the same test produce a different result.

Failures generate scattered evidence

Logs and measurements often remain on the individual machines that participated in the run.

A rerun is not always a reproduction

Repeating the same script does not recreate the same conditions unless the environment is preserved as well.

TS Factory

Automate the whole test environment around the script.

Test automation often focuses on triggering a script and checking the result. For complex systems, automation also needs to coordinate the infrastructure around that script. With TS Factory, a test workflow can include:

1

Prepare

Configure the machines, devices and services required for the scenario.

2

Coordinate

Run actions across multiple agents in the order required by the test.

3

Execute

Run large test sessions repeatedly across the same controlled setup.

4

Collect

Bring logs, measurements and results from participating systems into one place.

5

Restore

Return test resources to the expected state after the run.

6

Compare

Review behavior across sessions, builds and changing configurations.

Where test automation becomes difficult

Distributed test scenarios

One result may depend on actions happening across several hosts or devices.

Device labs

Physical resources have to be allocated, configured and restored between runs.

Long-running sessions

Thousands of tests may execute for hours or days and generate large volumes of diagnostics.

Integration and system tests

The workflow may cross APIs, services, firmware and hardware at once.

Changing configurations

Firmware versions, software builds and infrastructure settings need to stay associated with each run.

Failures that are hard to reproduce

The most valuable automated test is often the one that preserves enough context to recreate the original failure.

TS Factory is the testing layer inside Midair.

Distributed test execution

TS Factory

TS Factory is built for test scenarios that span multiple machines, devices and interconnected services.

It coordinates cooperating agents, executes large test sessions and gathers the resulting diagnostics in one system.

Investigation across the lifecycle

Midair

When TS Factory is used inside Midair, the test result can remain connected with static-analysis findings from Visao and runtime evidence collected by Delta.

That makes the automation workflow useful beyond pass or fail: the failed run becomes part of the investigation context.

What can be automated

Regression workflows

Run the same system-level scenarios across builds and compare the results over time.

Integration testing

Coordinate scenarios where several components or services participate in the same workflow.

Embedded and device testing

Automate execution across physical devices, test hosts and hardware-dependent environments.

Network and distributed systems

Run scenarios across multiple nodes, network devices or interconnected services.

Stress and long-running tests

Execute large sessions under sustained or changing conditions.

CI/CD validation

Trigger repeatable test workflows from existing delivery pipelines and keep the resulting context associated with the run.

Test automation should preserve reproducibility.

Automation saves time only if repeated runs remain comparable.

For complex environments, that means preserving more than the test code.

•

Software and firmware version

Know exactly which build was tested.

•

Participating agents

Record which machines or devices were involved.

•

Configuration

Keep the relevant environment settings associated with the run.

•

Inputs and scenario

Know which sequence of actions produced the result.

•

Logs and measurements

Collect diagnostics from across the participating systems.

•

Environment history

Track the changes made to the test setup and restore it afterwards.

Use the automation you already have.

Midair does not need to replace every existing test framework. Test automation can be introduced around the infrastructure and workflows you already operate.

Existing CI/CD pipelines

Trigger Midair or TS Factory from the delivery process you already use.

Existing test suites

Keep component-level or framework-specific tests and coordinate them as part of larger scenarios.

Physical devices and labs

Connect distributed agents to existing hardware and test infrastructure.

Cloud or on-premises environments

Run the testing layer where the system and test resources already live.

From scripts to reproducible test infrastructure

Test automation becomes infrastructure once other engineering work depends on it.

A reliable automation system prepares the environment, coordinates the resources involved and runs the test. It also preserves the result, so the same scenario can be investigated later.

TS Factory provides that execution layer, while Midair keeps the resulting evidence connected with the wider software lifecycle.

FAQ

What is test automation?

Test automation uses software to prepare, execute and evaluate repeatable test workflows without requiring each step to be performed manually.

What is distributed test automation?

Distributed test automation coordinates one test scenario across multiple machines, devices or services, where a single host is not enough to run it.

Does Midair replace existing test frameworks?

Not necessarily. Existing test suites and CI/CD workflows can remain in place while TS Factory coordinates larger distributed scenarios and Midair connects the resulting evidence.

Can TS Factory test physical devices?

TS Factory is designed for distributed environments that can include physical devices, test agents and multi-device labs.

Start with one test workflow.

Bring one scenario that currently requires manual setup, several machines or repeated investigation after a failure.

Connect it to TS Factory, automate the surrounding environment and keep every run available in Midair with the context that produced it.