remote-tests

From README

Test Fixtures Individual test cases must opt-in to being run against a remote executor. codexcore Use TestCodexBuilder::buildwithautoenv() to opt-in to remote execution in core integration tests unless the test needs more precise control over its executor. app-server Start the server with TestAppServer::newwithautoenv() unless the test defines its own $CODEXHOME/environments.toml or will define custom environments at runtime. Start threads with TestAppServer::sendthreadstartrequestwithautoenv() if you've created the server with the autoenv approach. Omit ThreadStartParams.environments (leave it as None) when doing so. Test Skips If a test doesn't pass in a particular remote executor configuration you can skip it in just that configuration. Include a string reason for future readers when the selected skip macro supports one. Choose the skip macro by what causes the test to fail: skipiftargetwindows!: Windows target behavior. skipifwineexec!: Wine-exec runner constraints.