Sandboxed execution
Builds and runs the change in an isolated environment to confirm it installs, starts and passes its checks before anyone relies on it.
Sub-techniques
2
| ID | Name | Description |
|---|---|---|
V1026.001 | Ephemeral environment | A fresh container or microVM per change with the repository's toolchain. |
V1026.002 | Reproduce-then-verify | Reproduce a reported bug in the sandbox, apply the fix, and show the same command now passes. |
Craft it
- Describe the environment as code (a Dagger pipeline or container image).
- Run the repository's own install, lint and test commands inside it.
- Keep the logs as evidence attached to the change.
Reverse engineer it
Signs that a codebase already runs this technique, and where to read how it is configured.
- dagger.json, devcontainer.json or a setup script used by CI.
- Bots that post reproduction logs on issues or PRs.
Open-source packages
3
- E2B e2b-dev/E2B
- Dagger dagger/dagger
- Testcontainers (Python) testcontainers/testcontainers-python