Crate: tools/minecraft-options
Commit: 2b2af1e4f8166d02e4732d19e040a53745d97a51
No test file imports analyze_options.py. Its parsing helpers, default resolution, normalization, compatibility matrix, report, and main (3000+ lines) have no regression protection, and every defect in the linked analyzer issues would have been caught by a small fixture of disassembly text (the ternary initializer, empty string, negative exponent, switch table, logarithm bounds, and legacy tri-state cases among them). Test layout would be small javap-text fixtures with a documented provenance in fixtures/options/SOURCES.md, run offline.
Unit tests cover the instruction parser, arithmetic and formula helpers, default and range resolution, legacy load and save analysis, enum extraction, keybinding decoding, normalize, and compatibility, using minimal deterministic fixtures. Ordinary runs need no javap or network.
Analyzer changes are validated only by regenerating data and reading diffs.
tools/minecraft-options/analyze_options.pytools/minecraft-options/test_*.pyConfirmed with a search for analyze_options in the test files.
1 comment
Closing as no longer valid. The analyzer is covered by offline tests in tools/minecraft-options/tests (javap tokenizer, option and OptionInstance analysis, default and range resolution, enum extraction, key binding decoding and key code spaces, numeric constants, extraction completeness, the graphics preset controls and the analyzer command line), and the compatibility matrix and report this issue lists were removed with the other research outputs nothing consumed.