OneTest / Docs

Product overview

OneTest components, use cases and typical workflow

OneTest consists of native C++ services and a browser UI. The services handle projects, plugins, runtime and recording; the UI runs in any browser.

Components

Component Role
OneTestServer Main service: projects, runtime scheduling and data distribution over HTTP / SSE / WebSocket
TargetRuntime Loads device plugins on each target machine
ModelRuntime Runs FMI/FMU models
DataRecorder Records data
TestExecutor Runs Python test scripts
Virtual device server Virtual avionics buses and I/O for hardware-free development

All services can run on one machine or be distributed across targets.

Platforms

Windows 10 / 11 x64 and Linux x86-64.

Current availability

This website currently introduces OneTest capabilities and use cases. Downloads and public API documentation are not available yet. Contact the team for an introduction.

Typical workflow

  1. Organize targets, devices, models and ICD data in the engineering studio.
  2. Validate with virtual devices or real hardware while inspecting health and live samples.
  3. Keep measurements and recordings as repeatable project records.