remote-tests

Run integration tests against remote executors using Docker or Wine environments.

5|1|Updated Jun 26, 2026
One-click install
npx skills add https://github.com/looooonk/better-codex --skill remote-tests-looooonk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: remote-tests
Source: https://github.com/looooonk/better-codex/tree/main/.codex/skills/remote-tests
Command: npx skills add https://github.com/looooonk/better-codex --skill remote-tests-looooonk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying that agent features work identically in local and remote execution environments is difficult, especially when the app-server and exec-server run on different platforms. This Skill provides the fixtures, skip macros, and commands needed to run integration tests against remote executors. ## Core Features & Use Cases - Remote Test Fixtures: Opt tests into remote execution with TestCodexBuilder::build_with_auto_env() for core tests and TestAppServer::new_with_auto_env() for app-server tests. - Targeted Skip Macros: Skip failing tests per configuration using skip_if_target_windows!, skip_if_wine_exec!, skip_if_host_windows!, skip_if_remote!, or skip_if_no_remote_env!. - Docker and Wine Runners: Execute core and app-server integration tests against a Linux Docker exec-server via scripts/test-remote-env.sh, or a Windows exec-server under Wine via Bazel targets. - Use Case: After modifying agent behavior in codex-core, run the full integration suite against a Docker remote executor to confirm the change works in the app-server/exec-server split before merging. ## Quick Start Run the codex-core integration tests against a Docker remote executor by sourcing scripts/test-remote-env.sh and invoking just test -p codex-core --test all.

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 the app-server equivalent. This builds and initializes a Docker container acting as the remote exec-server.

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

Tests must opt in explicitly. Use TestCodexBuilder::build_with_auto_env() for codex-core tests, or TestAppServer::new_with_auto_env() plus send_thread_start_request_with_auto_env() for app-server tests, leaving ThreadStartParams.environments as None.

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

Use the skip macro matching the failure cause: skip_if_wine_exec! for Wine runner constraints, skip_if_target_windows! for Windows target behavior, skip_if_host_windows! for Windows hosts, or skip_if_remote! for local-only tests. Include a reason string when supported.

Can I run remote executor tests on macOS?▼

Remote executor tests require an x86_64 Linux host, so they do not run directly on macOS. You can connect to a Linux devbox via ssh, reuse the codex checkout in ~/code/codex, and run the tests there.

Why do Wine remote tests only run under Bazel?▼

Wine tests cross-compile a Windows exec-server while the app-server stays on the Linux host, and that cross-platform build dependency is only wired up in Bazel. Use bazel test //codex-rs/core:core-all-wine-exec-test or the app-server target.