Batched background migration testing produces incorrect results when testing 2 migrations with the same class.
The data for each batched background migration is written into a directory based on the background migration class name.
This is an issue if the migration class is reused (such as with CopyColumnUsingBackgroundMigration
), as the testing framework overwrites the directory when testing the second migration.
Change the directory structure so that this overwriting doesn't happen.