Running Tests
🚧 Documentation under development
The RidgeRun Embedded Test Orchestrator guide is currently under active development. Some sections may be incomplete or change without notice.
Questions? Contact RidgeRun or email to support@ridgerun.com.
Running Tests
The dashboard can start one configured test or every test in a suite. Both options create a validation run and execute the selected scripts on the embedded device.
1. Check the Device Agent
Before starting a run, confirm that the device agent terminal is active and not reporting connection errors.
If the agent is stopped, start it using the commands in Starting the System.
2. Run One Test
- Select Devices from the top navigation bar.
- Open the target device.
- Find the test under Assigned tests on device (unique test IDs).
- Select Run.
The server creates a run containing only that test and opens the run details page.
3. Run a Test Suite
To execute all tests in a suite:
- Return to the device details page.
- Find the suite under Test groups.
- Select Run group.
The server creates one run containing every configured test in the selected suite.
4. Follow the Run
After a run starts, the dashboard opens Run RUN_ID'. The page initially shows the run and its items as queued or running.
The possible run states are:
| Status | Meaning |
|---|---|
queued
|
The run is waiting for the device agent. |
running
|
The device agent is executing the requested tests. |
passed
|
Every test completed successfully. |
failed
|
At least one test failed or could not complete successfully. |
Wait a few seconds, then refresh the browser page to load the latest status and results.
If a run remains queued, verify that the correct device agent is connected and using the same device ID shown in the run.
Next Step
The validation has been executed on the target hardware. Continue to Reviewing Results and Rerunning Tests to inspect the output and repeat an existing run.