Code Execution & Workspace Tool

The Test Runner Tool

Execute a project’s tests in the sandbox and return which passed, which failed, and why — so an agent can verify a change actually works before proposing to merge it.

Explore VDF AI Agents
SandboxedRuns in an isolated workspace
GovernedEvery action logged
AssignableTo any engineering agent
100%On-premise capable
The Execution Gap

A suggestion isn’t a shipped change

An agent that can only propose code still leaves all the work to a human. To actually deliver, it needs a real, governed workspace where it can run code, edit files, test, and use Git — safely, and without touching anything you didn’t allow.

01

Read-only agents

Suggestions still require a human to run, test, and commit everything.

02

Unsafe execution

Running agent-generated code on real infrastructure is a security risk.

03

No verification

Without tests and builds, an agent can’t know its change works.

04

Ungoverned Git

Direct repo access with no policy or audit is a non-starter in the enterprise.

How the Tool Works

Test Runner, without the risk

Capability

What it does

Run the test suite and report pass/fail.

it runs the project’s test suite in the sandbox and returns results, failures, and output.

Tool
Test Runner

Assignable to any agent

TestPass/FailVerifyParsed

How it works

Predictable, inspectable behavior

Designed to be reliable.

it detects or accepts the test command, runs it under resource limits, and parses the results, so an agent gets a definitive pass/fail signal rather than a guess about whether code works.

Governed
Policy + Audit

Every call logged

ScopedLoggedGovernedOn-prem

Governance

Private, governed, on-premise

Runs inside your perimeter.

Execution runs in an isolated, on-premise sandbox scoped per tenant with full command and file audit logging, so an agent can do real work on your code without unsafe access or anything leaving your perimeter.

100%
On-Prem

Per-tenant, logged

On-premRBACAudit logSovereign
Inputs

Parameters

The test_runner tool accepts these inputs when an agent calls it. Required inputs are flagged.

Name Type Required Description
command string Optional Test command to run; auto-detected if omitted.
path string
default: .
Optional Project directory.
filter string Optional Optional pattern to run a subset of tests.
In depth

How the Test Runner tool works in practice

Test Runner is a code execution & workspace tool you assign to a VDF AI agent. It runs the project’s test suite in the sandbox and returns results, failures, and output. Its hallmarks — Test, Pass/Fail, Verify — let an agent rely on it as a dependable step in a larger task rather than a brittle one-off script.

Under the hood, it detects or accepts the test command, runs it under resource limits, and parses the results, so an agent gets a definitive pass/fail signal rather than a guess about whether code works. Every call is scoped to the requesting tenant and written to an audit log, so the capability is safe to run inside a regulated, on-premise environment — the same governance model behind every VDF AI tool.

Teams reach for Test Runner when they need to handle change verification, regression guard, and TDD loops. It rarely works alone — pair it with Build Runner, Lint Runner, and Sandboxed Code Execution to build a complete, governed workflow, then compose those steps into an on-premise VDF AI Network.

Where it pays back

Where Test Runner pays back

Change verification

Prove a fix works before opening a PR.

Regression guard

Catch breakage an agent’s edit introduced.

TDD loops

Let an agent iterate until tests pass.

Gate merges

Block a change that fails the suite.

How VDF AI connects it

Assigned to agents, orchestrated as networks

On VDF AI, an industry’s use cases map to agents, and you assign tools like this one to those agents. Compose multiple agents into a governed, on-premise network.

ROI Snapshot

What changes after you assign it

Faster
From suggestion to shipped
Verified
Changes tested before merge
Traceable
Every command audited
100%
Code never leaves your perimeter
FAQ

Questions about the Test Runner tool

What is the Test Runner tool?

It runs the project’s test suite in the sandbox and returns results, failures, and output. Assigned to a VDF AI agent, it runs under role-based policy with full audit logging so the capability is safe to use in production.

Does it detect the test command?

Yes, for common stacks; you can also pass an explicit command or a filter to run a subset.

What does it return on failure?

The failing tests and their output, so an agent can diagnose and fix before retrying.

What inputs does the Test Runner tool need?

It has no strictly required inputs, and optionally accepts command, path, and filter. Each parameter is validated when an agent calls the tool, and the full call is logged for audit.

Which tools pair well with Test Runner?

Test Runner is commonly assigned alongside Build Runner, Lint Runner, and Sandboxed Code Execution. On VDF AI you compose several tools and agents into a single governed, on-premise network.

Does it run on-premise?

Yes. Like every VDF AI tool, it can run on-premise or in your sovereign cloud, scoped per user and audit-logged, so your data never leaves your perimeter.

How do agents use it?

You assign the tool to an agent under a role-based policy; the agent calls it as one step in a task, and several agents and tools can be orchestrated together as a governed VDF AI Network.

Put Test Runner to work

See the Test Runner tool assigned to an agent and orchestrated in a governed, on-premise network.