Reviewing Results and Rerunning 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.
Reviewing Results and Rerunning Tests
Every validation run keeps its overall status, individual test results, execution times, exit codes, and script output.
1. Open the Run History
Select Runs from the top navigation bar.
The table shows:
- The unique Run ID.
- The target Device.
- The current Status.
- Total, passed, and failed test counts.
- Creation and completion times.
Select Refresh to load recent status changes.
2. Open a Run
Select the Run ID that you want to inspect.
The summary identifies the device, status, requester, source run, and test totals.
Source run is empty for an original execution. A rerun displays the ID of the run from which it was created.
3. Review Each Test Result
The Run items table shows one row for each test execution:
| Field | Meaning |
|---|---|
| Index | Position of the test in the run. |
| Assigned Test ID | Configured test used for this execution. |
| Available Test ID | Manifest ID executed by the device agent. |
| Status | Execution progress or final state. |
| Result | Final PASS or FAIL result.
|
| Exit Code | Exit code returned by the test script. |
| Duration | Total execution time in milliseconds. |
4. Read the Test Output
Scroll below the run items table. Each test has a Logs section containing:
stdout: normal messages and validation evidence produced by the script.stderr: errors and diagnostic messages produced by the script.- An additional error message when the test could not execute normally.
Use the failed test ID, exit code, and logs together to determine what must be investigated on the target device. The Test Orchestrator reports the evidence; the development team decides whether the failure is a regression or an expected platform condition.
5. Rerun the Validation
To repeat the same configured tests on the same device, select Rerun run ID at the top of the run details page.
The dashboard creates a new run and opens its details page. The previous result is preserved, and the new run identifies the original execution under Source run.
A rerun is useful after correcting the device state, updating the software, or investigating a failure.
User Guide Complete
You can now manage devices, create tests, configure test parameters, build test suites, execute validations, and review their results. Use the navigation menu to return to any part of the guide when updating your validation setup.