CI Test Runner

Run a repo's test suite in a disposable sandbox and turn the output into a structured pass/fail report.

Beginner~5 minexecstrict: false

Run a repo's test suite in a disposable, CI-style sandbox and turn the raw output into a structured pass/fail report — the building block for a PR check, a bot, or an agent that needs to know "did the tests pass" without scraping a log.

Setup

Start OpenSandbox in Docker (one-time setup):

bunx alineo-cli init

Run it

cookbooks/ci-test-runner
$bun install
$bun start
Simulated preview — no sandbox is actually created here.Run it for real →

What it does

Scaffolds a tiny Python project (calc.py + test_calc.py) directly in the sandbox — one test deliberately fails, so you see a real failure report.

Installs pytest.

Runs the suite with strict: false so a non-zero exit is data, not a thrown error.

Prints a structured report (status, summary, and the full output on failure) and sets process.exitCode accordingly — the same shape a CI step or bot would check.

Point this at a real repository

Swap the "scaffold a project" step for a real clone:

await sb.exec(`git clone --depth 1 ${repoUrl} /workspace`);

Server proxy

All examples default to useServerProxy: true — traffic routes through the OpenSandbox server so Docker bridge IPs don't need to be reachable directly. Set USE_SERVER_PROXY=false to disable (e.g. when using uvx opensandbox-server on the host).