Docs

Test Runner

What this screen is for

Test Runner executes test suites on the platform and keeps their results. Runs execute on Argo Workflows, so a test run is a pipeline like any other — it can be watched, re-read, and compared with previous runs.

Before you start

To do this You need
Open Test Runner the Test Runner access permission

Argo Workflows must be connected and tested — see Settings › Development › CI/CD. Without it, runs submit and never start.

Opening it

  1. Tools › Test Runner in the sidebar.
Route Screen
/test-runner Dashboard of test runs
/test-runner/run Start a run
/test-runner/run/:id One run’s details

The interface

📸 Screenshot Placeholder: The Test Runner dashboard. Mark: (1) the Runner label showing Argo Workflows, (2) the Test Runs table, (3) the action that starts a run, (4) a row’s status.

# Control What it does When you’d use it
1 Runner label Names the execution engine — Argo Workflows Diagnosing why nothing starts
2 Test Runs table Past and current runs Reviewing results
3 Start a run Opens the run form Running tests
4 Status How a run ended Triage

Walkthroughs

Start a test run

  1. Tools › Test Runner, start a run.
  2. Fill in the form and submit.
  3. Watch the status. Runs execute on Argo Workflows, so the delay before it starts is the workflow being scheduled, not the UI being slow.

Read a run’s results

Open the run from the table. Its details page carries the outcome and the output.

Scenario

Test runs submit but never start.

  1. Tools › Test Runner — check the Runner label. It reads Argo Workflows, which tells you where to look next.
  2. Go to Settings › Development › CI/CD.
  3. Find the Argo Workflows integration — not the Argo CD one; they are separate, and having deployments work proves nothing about workflows.
  4. Read Last Tested. Empty means it has never been proven to work.
  5. Test the integration. The error names what is unreachable.
  6. Check the integration’s location type against where Argo Workflows actually runs. A wrong location saves successfully and fails only in use.
  7. Re-submit the test run.

This is the same diagnosis as pipelines that never start, for the same reason: both ride on Argo Workflows.

When it doesn’t work

Symptom Cause How to check Fix
Test Runner is not in the submenu Missing the Test Runner access permission Access Explorer Ask for a role granting it
Runs submit but never start Argo Workflows integration missing or untested CI/CD Add and test the Argo Workflows integration
Deployments work but tests do not Only Argo CD is connected The CI/CD Type column Argo Workflows is a separate integration
A run failed immediately The suite’s own preconditions The run details Read the run output
No history Nothing has been run yet on this install — Expected

Next