Abstract schema changes are currently not testable in PHPUnit. If a schema change file is invalid, or if a JSON file isn't used to (re-)generate .sql files, no test will fail. The only ways to tell that something is amiss are other tests that happen to use the schema (which isn't always the case, and for things like changing the default or type of a column, general-purpose tests may not catch it), and human reviewers.
Ideally, we would have a structure test that validates all the schema files specifically, and instructs the developer on how to fix the problem.
This was first being discussed in T237839 (wiring abstract schema to extension.json), but there hasn't been any progress on that task for two years, and there generally seems to be disagreements on the format of the proposed attributes. So, I am proposing that we start off by providing a structure test that doesn't rely on extension.json. The test could be made opt-in, like ExtensionJsonTestBase. It could later be deprecated in favour of (probably) a test method in ExtensionJsonTestBase itself, when T237839 is done.