Orcraft 1.1.3 public beta released 08-Nov-2026. The Free Plan and the Team trial are open; card payments and invoices open shortly.

Orcraft 1.1.3 public beta released 08-Nov-2026. The Free Plan and the Team trial are open; card payments and invoices open shortly.

Orcraft

The platform for test development and orchestration
that lets you and your AI Agents run the entire testing operation

Watch the demo

Running Hello World test

With the test's code reviewed, let's run it. As code developers, we'll start from the CLI, then revisit the same run through the controller's GUI, which the Getting started guide already walked through click by click.

Running from CLI

The test's main function makes it directly runnable as a script - from the test's own directory:

cd orcraft-test-suite-tutorial/test_group_intro/test_hello_world
python test_hello_world.py

ANSI output

The framework provides structured, formatted output for each stage of the test, from configuration to results:

Orcraft Controller (v0.1.0.dev149)
----------------------------------

                                    Test: Hello World | Description                                     

This is a minimal implementation of an Orcraft Test.
It demonstrates how to define a test config, inherit from OrcraftTest, and implement a single test case.
When executed, the test logs a simple Hello World message and returns a passing test result.


     Test: Hello World | Configuration      

Name              | Start Time
--------------------------------------------
Test: Hello World | 2026-09-02  19:21:08.453

    [TestHelloWorld] Hello World

                     Test: Hello World | Result                     

Name              | Status | Finish Time              | Elapsed Time
--------------------------------------------------------------------
Test: Hello World | PASS   | 2026-09-02  19:21:08.455 | 0.002 s

Notice the Hello World name and description in the output - these are exactly the name and description fields set on TestHelloWorldConfig earlier. The rest of the output - timing, the configuration table, the pass/fail result - is the framework at work: the test itself only logged one line, and the framework did everything else. Each of these built-in pieces is covered in its own place, later in this tutorial and in the Framework section.

Log files

This same output is also saved alongside the test, in a Logs folder created next to it:

cd Logs
ls
Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a---          2026-09-02    19:21           1013 Test__Hello_World__2026-09-02__19-21-08.452.ansi

Running from GUI

Running this test from the controller's GUI - adding the suite, selecting the test and starting the run - is already covered step by step in the Getting started guide.

Test log

The controller's GUI shows the very same log shown earlier in the ANSI output section:

Type to search the docs.

    ↑↓ navigate ↵ open Esc close