AutoTester: Docker-based in-game integration test framework#491
Draft
Skidamek wants to merge 16 commits into
Draft
AutoTester: Docker-based in-game integration test framework#491Skidamek wants to merge 16 commits into
Skidamek wants to merge 16 commits into
Conversation
Adds a docker-based autotest framework that runs real Minecraft server + client containers, drives the UI through a file-based JSON bridge (AutoTestBridge), and validates the modpack sync flow against 22 version/loader targets. Includes mod-side changes required to expose UI state for testing: AutoTestBridge, async certificate trust helpers, EditBox inputText persistence, and infrastructure cleanup for unsupported MC versions.
Adds a docker-based autotest framework that runs real Minecraft server + client containers, drives the UI through a file-based JSON bridge (AutoTestBridge), and validates the modpack sync flow against 22 version/loader targets. Includes mod-side changes required to expose UI state for testing: AutoTestBridge, async certificate trust helpers, EditBox inputText persistence, and infrastructure cleanup for unsupported MC versions.
…re discovered via autotester
…sions + better docs why
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a full autotester framework that spins up headless Minecraft server + client Docker containers, drives the in-game UI via
AutoTestBridge(file-based JSON bridge), and validates real UX flows e.g. (connect -> fingerprint -> sync/update -> restart -> rejoin) across all 20 version/loader targets.What's included
autotester/Python package - phase-driven runner with declarative YAML scenarios:cli.py-autotester build-images,autotester run,autotester cleanrunner.py- phase orchestration + Docker lifecycle (containers, networks, volumes, log waits, cleanup)bridge.py- pollsbridge-command.json/bridge-response.jsonevery 50ms with a 30s timeoutconfig.py- YAML loading forsettings.yaml,targets.yaml,scenarios/*.yamlsync(full end-to-end + rejoin) anddownload-only(no restart, faster debug)AutoTestBridge.java- registered via mod initializers; exposes:ping,get_screen,get_widgets,click,set_text,set_screen,connect,verify_fingerprint,quitCI (
.github/workflows/ingame-tests.yml):preparebuilds the target matrix fromtargets.yamlbuildreuses the shared build workflow (build.yml) and publishes merged jars asbuild-artifactsingameruns afail-fast: falsematrix, downloads artifacts, builds the client image, and runs the scenarioreportaggregatesresults.json, emits::errorannotations, and posts a summary table to$GITHUB_STEP_SUMMARYInfrastructure cleanup:
How to run