Summary

We have our standard upgrade/downgrade compatibility testing compatibility_test_for_releases.sh, which uses test/format and test_checkpoint. The combination of these two tests handles a lot of general-purpose checking using an approach similar to fuzzing. Starting with WT-10533, we also now have smaller upgrade/downgrade compatibility unit tests targeted towards checking specific scenarios.

Now that we have more than just one test, we would like to rethink our approach to compatibility testing.

Proposed Approach

WT-10533 adds a new directory for compatibility tests, test/compatibility. We would like to:

• Move compatibility_test_for_releases.sh to this directory.
• Explore providing better infrastructure for running the compatibility unit tests, such as by sharing some common functionality from wttest.
• Consider writing a separate runner for the compatibility unit tests.