Introducing RidgeRun Embedded Test Orchestrator

oscarporras7
a few seconds ago
2 min read

Embedded products become harder to validate as they evolve. New drivers, peripherals, services, and hardware configurations increase the number of components that must continue working after every software change.

When validation happens late, several changes may already be involved. Developers spend more time identifying the cause, QA work may need to be repeated, and releases can be delayed.

Frequent validation keeps regressions closer to the changes that introduced them.

Obtained from: Functionize.

The longer a regression remains hidden:

More changes become possible causes, making the responsible change harder to identify.
More engineering teams may be interrupted to investigate and correct the problem.
More validation work must be repeated after a corrected build is delivered.
Release dates and customer commitments face greater risk.
One failure may hide others, delaying the discovery of additional problems.

This is where RidgeRun Embedded Test Orchestrator makes a difference.

RidgeRun Embedded Test Orchestrator helps teams execute repeatable validation directly on embedded hardware. How does it achieve it? The process is simple:

Connect your devices: An embedded agent reports device availability and the tests it can execute.
Add your testing scenarios: Customizable Bash scripts validate the interfaces, peripherals, drivers, and system behavior required by your product.
Run and review: Start test suites from the web dashboard and review their status, results, and generated logs.

Existing manual procedures become reusable tests that can be executed consistently across devices and software versions.