blacksmith-testbox

To reproduce a CI environment locally, warm up a remote Testbox that mirrors the exact CI parity, provisions required hosted services, and injects necessary secrets for your integration tests.

The best way to inject secrets and provision hosted services is by using a remote Testbox to apply credentials and services that local iterations cannot reproduce, ensuring accurate workflow validation.

To run commands from the repository root in a remote testbox, warm up the Testbox first, then execute your project commands using the returned ID while the system enforces running from the repo root and syncing only delta changes.

You should use a remote testbox instead of local iteration when your repo workflows require strict CI parity, secrets provisioning, or hosted services that your local environment cannot reproduce.

Yes, you can download artifacts after executing a remote testbox run by using the run and download flows provided, which manage artifacts generated during the remote execution of your project commands.