Documentation

Run enterprise-app validations remotely. Velo absorbs the runtime. Integrate via REST or your test engine.

Start

What Velo is, how a first run works, and the five concepts the rest of the docs assume.

The app surface under test — UI or headless — decides whether a suite can run remotely.

Trigger Velo from REST, from Robot, or from the ALM tool you already use.

The same four steps whether you come in through REST or velo robot.

Engine-native (Robot / Copado) or REST (Rev-Trac, CI).

velo login --engine robot-sap
velo robot ./tests

# or
POST /suites          engine=robot-sap
POST /executions      suite_id, strategy

Clients first, then engines, then how you trigger a run.