remote-tests

Launch a Docker executor for remote test execution in Linux environments.

4|1|Updated Oct 5, 2024

Search Tags:#integration #docker #environment #remote #run #tests #devbox

Ready to run

npx skills add https://github.com/xrehpicx/anya --skill remote-tests-xrehpicx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: remote-tests
Source: https://github.com/xrehpicx/anya/tree/main/.codex/skills/remote-tests
Command: npx skills add https://github.com/xrehpicx/anya --skill remote-tests-xrehpicx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill enables running tests against a remote executor inside a Docker container, allowing teams to validate integrations without local setup and to reproduce CI-like environments.

Core Features & Use Cases

Remote test execution against a dedicated Linux/devbox environment using a docker-based executor.
Script-driven initialization via scripts/test-remote-env.sh to bootstrap the remote test environment.
Ideal for CI workflows, offloading testing from the local machine, and validating code against external test suppliers.

Quick Start

Run the remote test workflow to spin up a docker-based executor and run the test suite.

Frequently Asked Questions about remote-tests

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

FAQPage Schema

How do I run tests remotely inside a Docker container?▼

To run tests remotely, this skill launches a Docker-based executor when the CODEX_TEST_REMOTE_ENV environment variable is set, bootstrapping the environment via scripts/test-remote-env.sh. It connects via SSH to a remote checkout and validates SHA and file synchronization.

What prerequisites do I need to execute remote tests on a devbox?▼

Executing remote tests on a devbox requires a Docker-enabled environment, a remote host accessible via SSH, and the initialization script at scripts/test-remote-env.sh. It applies specifically to Linux environments and devboxes.

How does the remote test executor validate file synchronization?▼

The remote test executor validates file synchronization by guiding users to SSH into a remote checkout and verify the SHA. This ensures the remote environment matches the local state before running tests.

Can I use this to reproduce CI-like environments for integration testing?▼

Yes, you can reproduce CI-like environments for integration testing. The skill runs test suites against a dedicated Linux or devbox environment using a Docker-based executor, validating integrations without requiring local setup.

Do I need a local Docker setup to offload test execution to a remote host?▼

You need a Docker-enabled environment and a remote host accessible via SSH to offload test execution. The initialization script at scripts/test-remote-env.sh handles bootstrapping the remote Docker executor.

Why is the remote test environment not working on my local machine?▼

The remote test environment only applies to Linux environments and devboxes. If the CODEX_TEST_REMOTE_ENV variable is not set or the initialization script scripts/test-remote-env.sh is missing, the Docker-based executor will not launch.