Native control, inspection, UI automation and evidence capture for a running Witcher 3 process.
1 folder · 32 files

live
__init__.py
README.md
test_asset_lz4.py
test_background.py
test_build_recovery.py
test_cli.py
test_compatibility.py
test_control.py
test_crossbow_input.py
test_crossbow.py
test_debug_export.py
test_debug_startup.py
test_debugger.py
test_encounters.py
test_experiments.py
test_game_paths.py
test_game_settings.py
test_heal.py
test_installation_state.py
test_lab_lifecycle.py
test_native_build.py
test_native.py
test_overlay_list.py
test_overlay.py
test_pe_image.py
test_performance.py
test_request_algorithm.py
test_runner.py
test_teleport_observation.py
test_ui_driver.py
test_water_depth.py
test_workspace.py
README.md

Verification #

Offline tests live directly in this package. From the repository root:

python3 -m unittest discover -s . -p 'test_*.py' -q

Do not treat a successful zero-test run as verification. The current suite has 384 tests; update that reference only when tests are deliberately added or removed. Test fixtures under ../fixtures/ are source data, not progress saves or raw session captures.

live/ contains explicit game-backed qualification harnesses, separate from unit-test discovery. They load a named, hash-checked save and control the game. Use one through its module entry point, such as python3 -m tests.live.debug_acceptance, only after checking owner/process, source/build, fixture and cleanup budget. Retain the result and exact save/mod/settings audits, including failures. No live harness runs during the offline unittest command.