Remote Tests
- 1 installs
- Updated May 4, 2026
- manaflow-ai/codex
Explains running Codex integration tests against a remote executor in a Docker container on a Linux devbox via the CODEX_TEST_REMOTE_ENV variable.
About
A guide for running Codex integration tests against a remote Docker executor on a Linux devbox. A developer uses it when tests require the remote executor path set via CODEX_TEST_REMOTE_ENV.
- Uses CODEX_TEST_REMOTE_ENV plus test-remote-env.sh to build the container
- Linux-only; connect to a codex devbox and reuse one checkout
Remote Tests by the numbers
- 1 all-time installs (skills.sh)
- Ranked #1,746 of 2,154 Testing & QA skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/manaflow-ai/codex --skill remote-testsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| Last updated | May 4, 2026 |
| Repository | manaflow-ai/codex ↗ |
What it does
Explains running Codex integration tests against a remote executor in a Docker container on a Linux devbox via the CODEX_TEST_REMOTE_ENV variable.
Files
Some codex integration tests support a running against a remote executor. This means that when CODEX_TEST_REMOTE_ENV environment variable is set they will attempt to start an executor process in a docker container CODEX_TEST_REMOTE_ENV points to and use it in tests.
Docker container is built and initialized via ./scripts/test-remote-env.sh
Currently running remote tests is only supported on Linux, so you need to use a devbox to run them
You can list devboxes via applied_devbox ls, pick the one with codex in the name. Connect to devbox via ssh <devbox_name>. Reuse the same checkout of codex in ~/code/codex. Reset files if needed. Multiple checkouts take longer to build and take up more space. Check whether the SHA and modified files are in sync between remote and local.
Related skills
TddFollow test-driven development with a strict red-green-refactor loop when creating reliable features or fixing bugs.544k196k
Test Driven DevelopmentEnforce writing failing tests before any production implementation code.181k264kQaRun conversational QA sessions that turn user-reported bugs into well-written, domain-aware GitHub issues without manual ticket writing.179k196kMigrate To ShoehornAutomatically update TypeScript test files that rely on unsafe `as` type assertions by replacing them with type-safe partial objects from @total-typescript/shoehorn.164k196k
Webapp TestingVerify frontend behavior, debug UI issues, capture screenshots, and inspect logs of a running local web application using Playwright.123k165k
Playwright CliRun browser automation, generate element snapshots, inspect DOM attributes, and execute Playwright tests from the terminal.102k12.3k