Assigning and Configuring 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.

Follow us on:

Share This Page

Facebook Twitter LinkedIn WhatsApp Email Copy Link

Close

Send Email Using

Gmail (Web) Thunderbird (default mail app)

Close

RidgeRun Embedded Test Orchestrator

< >

RidgeRun Embedded Test Orchestrator from RidgeRun

Contents Pin

• Introduction
  • How Much Does a Bug Cost You?
  • What Problem This Solves
  • What RidgeRun Is Offering
  • Is the Test Orchestrator Right for Your Project?
  • What the Test Orchestrator Does Not Replace
• How the Test Orchestrator Works
  • System Overview
  • Validation Process
  • Key Concepts and Terms
• Getting Started
  • System Requirements
  • Installation
  • Starting the System
  • Running Your First Test
• Contact Us

Assigning and Configuring Tests

Info

Before You Begin: Create and discover a test by following Creating Test Manifests.

An available test describes what the device agent can execute. Assigning it to a device creates a configured test with the parameter values required for that device.

1. Open the Device

1. Open the dashboard.
2. Select Devices from the top navigation bar.
3. Select the device ID.

The Available tests (from agent manifests) table shows the manifests reported by the device agent.

2. Find the Test

Use Filter available tests by ID or name to find the required test.

Review its runner, entry point, timeout, tags, and parameter names before assigning it.

Info

Screenshot Placeholder: Device details page filtered to show one available test. Suggested file name: test-orchestrator-filter-available-tests.png.

You can also use Available Tests in the top navigation bar to inspect every test reported by a selected device. That page is read-only; tests are assigned from the device details page.

3. Select and Configure the Test

Under Add test to device:

1. Select the test from the list.
2. Review each displayed parameter and its default value.
3. Replace any value that must be different for this device.
4. Select Add selected available test.

For the network_interface_check example, set interface_name to the interface that exists on the target, such as eth0 or eno1.

Info

Screenshot Placeholder: Add test to device form showing a selected test and a configured parameter. Suggested file name: test-orchestrator-configure-test.png.

Boolean parameters provide true and false options. Number and integer parameters accept numeric values. Empty optional values use the manifest configuration when available.

4. Confirm the Assigned Test

The test appears under Assigned tests on device (unique test IDs). Confirm the following values:

• Assigned Test ID: unique identifier for this configured test.
• Available Test ID: manifest ID reported by the agent.
• Name and Runner: test information from the manifest.
• Parameters: values that will be passed to the script.

Info

Screenshot Placeholder: Assigned tests table showing the new test, its unique assigned ID, parameter value, Run button, and Delete button. Suggested file name: test-orchestrator-assigned-test.png.

The assigned test is now ready to run by itself or to be included in a test suite.

5. Remove an Assigned Test

To remove a configured test, select Delete in its row.

Removing an assigned test does not delete its script or manifest from the embedded device. The test remains available and can be assigned again with new parameter values.

Info

Important: Remove the test from any test suite before deleting it.

Next Step

You now have a test configured for the target device. Continue to Creating Test Suites to combine configured tests into one validation sequence.

RidgeRun Embedded Test Orchestrator

Back to top ↑ < >