test

Arguments and rejection

Accept zero or one entry operand, the listed compiler and package selectors, and program arguments after --. A selected entry with --root naming a package must be an admitted file under that package root.

With no entry, test the package entry. Reject standalone --locked, unsupported JSON output, export inspection, profile selectors, and invalid program input signatures before execution.

Output

Program output uses standard output. Default SELF execution streams output through the native host. The test completion rule → defines the success and failure footers.

Deferred-action errors use standard error and make the test fail. A test with a deferred-action error must not print test-ok, even when its main result is Ok(0). --format json is rejected and no JSON report is supplied.

Exit status

Exit 0 means checking and test execution succeeded with no deferred error and a zero process result. Argument, package, checking, assertion, runtime, deferred-action, and host failures exit 1.

An admitted explicit main returns Result<int, string>. Ok(code) with an integer from 1 through 255 is preserved as a failing process exit. Err(message) writes the string to standard error and exits 1. Out-of-range codes and invalid result shapes fail with exit 1.

Filesystem effects

Read source, package metadata, lock data, and any declared replay input. Default SELF execution uses the native host. Runtime file operations follow that host's capabilities and can change admitted files. Those program effects remain after a failure. Compiler setup does not rewrite source, manifests, locks, or vendor content and may use owned temporary files.

Network access

Compiler setup and package loading perform no registry or network access. Runtime network behavior follows the executed program and its available operations. Declared extern replay supplies the configured external-call results.

Reproducibility

Repeatability depends on the selected runtime host, source graph, dependencies, compiler, program arguments, standard input, environment, files, clocks, randomness, replay data, and external service responses. Equal source bytes alone do not determine a native test's output or exit status.

Packages and locks

Package checks and required lock validation finish before the test starts. A selected entry uses its package's dependencies when the explicit root contains a manifest. Missing dependencies never trigger a fetch.

Registry dependencies or Lispex configuration require explicit --locked, even when a matching lock exists. Without that option, a local-only package can load declared path dependencies by their expected hashes. Locked loading rejects missing or stale state and never repairs it.

Standalone entry mode rejects --locked. Selected-entry test is the exception when an explicit root contains the package manifest and the entry belongs to that package.

The invocation topaz test main.tpz --language-version 5.21 --format json is expected to exit with 1.