Welcome to ETOS’s documentation!


ETOS (Eiffel Test Orchestration System) is a new test orchestration system which takes away control of how to run and what to run from the system itself and places it into the hands of the relevant engineers.

The idea of having a system dictate what and how to run is finished. Let’s bring back control to the testers.

With ETOS we define how to run tests using recipes and we define what to run with collections of recipes.

ETOS Roles
Test Engineer Test Automation Engineer System Engineer
Create collections Create recipes Deploy ETOS
Analyze results Create tests Infrastructure
What to run? How to run? Where to run?

This means that only people who knows how and what to run decide these factors. ETOS will only receive the collection of recipes and executing it accordingly. You can also mix test suites. For instance, let’s say you want to run a “go” unittest and a “python” function test in the same suitt, that’s easy to do; just add them to your collection.

This is the strength of ETOS. Relying on the humans to decide what to run, how to run and where to run.

ETOS is a collection of multiple services working together. This repository is a facilitator of versioning, helm charts and documentation. The services are located in these repositories.


  • Generic test suite execution based solely on JSON.
  • Mix and match test suites, regardless of programming language.
  • Separation of concerns between testers, test automation engineers and system engineers.
  • Eiffel protocol implementation.


TBD (Helm)


Please write issues in the relevant repositories for where you found the issue.
If you do not know which repository to write the issue for, feel free to write it here and it will be moved.
Documentation issues are reported here.

Indices and tables