AXSG changes both compile-time semantics and runtime behavior, so the test strategy is intentionally broad.
These lock small parser, binder, emitter, runtime-helper, and language-service rules.
These validate the generated C# shape directly. They are important for:
These verify generated code and runtime helpers cooperate correctly when features are executed, not just emitted.
These make sure editor features follow compiler semantics and survive transport/projection layers.
These validate whole-project behavior, package outputs, build graph wiring, and compatibility scenarios.
If you are changing AXSG or integrating deeply with it, the test suite tells you where confidence comes from. A feature page might look simple, but its behavior may be locked by several kinds of tests across compiler, runtime, and editor layers.