skills.rest
sjc786526-coder
sjc786526-coderCOMMUNITY
Explore all skills by this author →
GitHub

remote-tests

Runs integration tests against remote executors via Docker or Wine environments.

Updated Aug 4, 2026
Search Tags:#integration testing#docker#rust#test fixtures#bazel#wine#remote executor
One-click install
npx skills add https://github.com/sjc786526-coder/RONDO --skill remote-tests-sjc786526-coder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: remote-tests
Source: https://github.com/sjc786526-coder/RONDO/tree/main/multidev/.codex/skills/remote-tests
Command: npx skills add https://github.com/sjc786526-coder/RONDO --skill remote-tests-sjc786526-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It ensures agent features work identically in both local and remote execution environments by exercising the app-server/exec-server split, catching bugs that only appear when code runs on a remote executor. ## Core Features & Use Cases - Remote Test Opt-In: Use TestCodexBuilder::build_with_auto_env() in core tests and TestAppServer::new_with_auto_env() in app-server tests to run against remote executors. - Two Executor Flavors: Run tests against a Linux exec-server in Docker via scripts/test-remote-env.sh, or a Windows exec-server under Wine via Bazel targets. - Granular Test Skips: Skip tests per configuration with macros like skip_if_wine_exec!, skip_if_remote!, or skip_if_no_remote_env! when behavior legitimately differs. - Use Case: After adding a feature to the app-server, run the full integration suite against a Docker remote executor to verify thread start requests and environments behave the same as local execution. ## Quick Start Run the core integration tests against a Docker remote executor by sourcing scripts/test-remote-env.sh and then running just test -p codex-core --test all from the codex-rs directory.

Frequently Asked Questions about remote-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run integration tests against a remote executor?▼

Source scripts/test-remote-env.sh in bash, set a cleanup trap with codex_remote_env_cleanup, then run just test -p codex-core --test all or just test -p codex-app-server --test all from the codex-rs directory.

How do I make a test run against a remote executor?▼

Use TestCodexBuilder::build_with_auto_env() for core integration tests, or TestAppServer::new_with_auto_env() for app-server tests. For thread starts, call send_thread_start_request_with_auto_env() and leave ThreadStartParams.environments as None.

Can I run remote executor tests on macOS or Windows?▼

Remote executor tests require an x86_64 Linux host. On macOS you can use a devbox: list them with applied_devbox ls, connect via ssh, and reuse the existing codex checkout in ~/code/codex.

How do I skip a test that fails only on Wine or remote executors?▼

Use the skip macro matching the failure cause: skip_if_wine_exec! for Wine runner constraints, skip_if_remote! for local-only behavior, skip_if_no_remote_env! for remote-only tests, or skip_if_target_windows! and skip_if_host_windows! for Windows-specific issues.

Why do Wine remote tests only run under Bazel?▼

Wine tests build a Windows exec-server and run it under Wine while the app-server stays on the Linux host. This cross-platform build dependency means they only run via Bazel targets like //codex-rs/core:core-all-wine-exec-test.

Related Skills

Explore More Software Engineering Skills→
adminlove520adminlove520

remote-tests

Run Codex integration tests against a remote docker executor via scripts/test-remote-env.sh.

Community
Intermediate
adamfeldmanadamfeldman

do:merge

Retry deferred Git worktree merges into the main branch.

Community
Advanced
streamlitstreamlit
45.5k

discovering-make-commands

List all available Make targets in the repository for build, test, lint, and format tasks.

Official
Basic
edgeandnodeedgeandnode

code-test

Run targeted cargo test commands for Rust workspace code changes.

Official
Intermediate