Orcraft and CI servers
Orcraft does not replace Jenkins, GitHub Actions or GitLab CI. It runs inside them. The pipeline triggers the run; Orcraft carries it out on the lab's machines and collects the results.
See the note on other products
Side by side
| Orcraft | CI server | |
|---|---|---|
| Its part in a test run | Sends the test package to the endpoints, runs the plan and collects the results | Starts the run on an event: a merge, a schedule, a button |
| What a run is made of | A Python suite, and a snapshot of a run exported from the controller | Jobs and stages written in the pipeline's own file |
| Machines | The runner as the controller, and the endpoints, the test machines registered in the controller. Every step runs on the machine it names | The runner where the job runs |
| Results | Logs from every machine and results rolled up from step to suite | The job's status and its console output |
A run from a pipeline
A CI runner is a controller installation that runs from the command line. A run is configured and confirmed in the controller's GUI and exported as a snapshot; the pipeline runs that snapshot. It is the same suite with the same plan, so a run that works in the GUI works in CI.
There is no pipeline glue to write for each test. Sending the package to the endpoints, running the plan and collecting the results are Orcraft's part.
The lab's machines
The pipeline's runner does not have to reach the hardware itself. The steps of a test run on the endpoints: Windows, Linux and macOS machines with the endpoint application installed, each one a machine that can reach a device under test, an instrument or a vendor's tools.
AI agents
A CI snapshot is plain Python: a batch file, and for each exported item a small class that overrides only what the run changed. So an AI agent can prepare a snapshot itself, in the same form the controller exports, extend one that exists with another test or with other values, and run it from the command line as the pipeline does. The batch loads back into the controller, where the same run shows in the GUI.
Every part of the work can be done by a person or by an AI agent: writing the tests, configuring a run, running it on the lab's machines and reading the results. The AI Agents section shows how.
All other product names are trademarks of their respective owners and are used for identification and comparison purposes only. Orcraft is not affiliated with, sponsored by or endorsed by any of them. The descriptions of other products on this page compare features and functionality to help you decide whether Orcraft fits your needs; they are not intended to disparage any product or its owner. They are summaries written by us, reflect our understanding at the time of writing, and may be inaccurate or out of date. For an accurate description of any product, visit its own site. If you believe a description is wrong, tell us and we will correct it.