mirror of
https://github.com/google/nomulus
synced 2026-02-08 05:50:24 +00:00
bb5d2dcf0a
* Use the DatabaseMigrationSchedule to determine which TM to use We still allow the "manual" specification of a particular transaction manager, most useful in @DualDatabaseTest classes. If that isn't specified, we examine the migration schedule to see which to return. Notes: - This requires that any test that sets the migration schedule clean up after itself so that it won't affect future test runs of other classes (because the migration schedule cache is static) - One alternative would, instead of having a "test override" for the transaction manager, be to examine the registry environment and only override the transaction manager in the UNIT_TEST environment. This doesn't work because there are many instances in which tests simulate non-test environment.