Version upgrade test

when a module changes between two publications (let’s say 5.6 to 5.8), process to reformat the database is handled if necessary.
New module is tested, ok. But do these tests include the test of the format change ? so version 5.8 tests will notify that db reformatting was wrong ? In other words, tests to prove that the old db is correctly reformatted.
I hope my question makes sens.

Unfortunately we currently do not test those format changes.

Currently this is manually tested, if there is any issue in the migration we fix on a minor release of the new series.

I’m not sure if it’s worth automating this tasks because normally they won’t break on newer versions.

What we need the most is testing migrations with real data before the release is frozen. This will help to detect most of the issues and fix them before the next release.