Backward-compatibility test coverage #545
Comments
joschi
pushed a commit
that referenced
this issue
Jul 25, 2023
- Attempts to be exhaustive on backward-compatibility coverage to raise confidence that future refactors will not introduce unintended regressions. - Each incompatible condition is tested separately by comparing two spec files where the only difference is that fine-grained incompatible condition. - In some cases the current behavior appears incorrect. Tests are still added for these to avoid unintended regression, but are given TODO comments for later follow-up. - Pre-existing tests have been removed if they are redundant to avoid confusion and to follow the convention. Closes #545
joschi
pushed a commit
that referenced
this issue
Dec 16, 2023
config-file and config-prop CLI options - Gives user fine-grained control of what constitutes an incompatibile change. Maven plugin config parameters - configFiles param for a separate yaml config file Corresponds to CLI --config-file option. - configProps param for specifying config props in pom.xml. Corresponds to CLI --config-prop option. - OpenApiDiffMojoTest updated to verify parameters work. Relies on recent exhaustive testing of incompatible checks to ensure no regressions (see #545). Fix #551 Fix #550 Fix #303
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Coverage is currently very light. Improvement here will enable future refactors to be made with confidence that no unintended regressions are being introduced. Additionally the improved testing will act as executable documentation, which in turn will improve adoption, contribution, etc
The text was updated successfully, but these errors were encountered: