claudes_game/continue.md

Test Refactoring Optimization Strategy

Tooling

• scripts/sim_engine.py — Generic orbital mechanics simulator (Python, TOML 1.0 configs)
  • Replicates C++ physics: Kepler propagation, orbital↔Cartesian transforms, drift detection
  • Multi-body hierarchical propagation with global/local coordinate tracking
  • Use for precalculating expected values (transition times, final states, energy conservation)
• TOML configs in tests/ must use TOML 1.0 inline table syntax (single-line {})
  • Old configs in old_tests/ use multiline inline tables (toml-c17 style) — keep for reference
  • Python's tomllib requires single-line inline tables

1. Structure

• One SCENARIO("description") per logical test group, with [tag1][tag2] annotations
• Shared fixture: all constants, structs, and variables declared between SCENARIO opening and first SECTION
• Precompute expected values analytically at fixture level (use scripts/*.py for complex simulations)

2. Duplication elimination

• Use lambdas that capture the fixture for repeated setup→call→assert patterns
• Reuse shared structs in-place (mutate fields rather than recreating)
• Single-line SECTIONs when body is one statement: SECTION("name") { helper(arg); }

3. Assertions

• using Catch::Matchers::WithinAbs; after includes
• REQUIRE_THAT(value, WithinAbs(expected, tolerance)) — never Approx()
• Tolerances based on actual observed errors, tightened aggressively (1e-12 for angles, 1e-6 for meters, etc.)
• Replace qualitative checks (a > b) with quantitative (WithinAbs(expected, tol))
• INFO("label: " << value) for debugging context

4. Precalc scripts

• For each test file, create scripts/precalc_<test_name>.py that computes expected values.
• Use scripts/sim_engine.py for physics (orbital_to_cartesian, propagate, etc.).
• Output C++-style comments with precalculated constants for embedding in the test.
• Run with: python3 scripts/precalc_<test_name>.py
• If sim_engine.py lacks a feature (e.g., spacecraft, OrbitTracker), use analytical formulas instead (but notify the user what feature was missing)

5. Process per file

• Process one test file at a time.
• Create scripts/precalc_<test_name>.py and run it to get expected values.
• Copy from old_tests/ to tests/, rewrite using the pattern from test_true_anomaly_roundtrip.cpp.
• Rewrite TOML configs to TOML 1.0 inline table syntax (single-line {}).
• Build and verify: make test-build then ./build/orbit_test '[tag]' -s.
• Run full suite: make test.
• Replace broken tests (e.g., OrbitTracker bugs) with working alternatives using propagation checks.
• Always ask for review before moving to the next file.
• Only commit when asked.