Define how to test migrations that include EE code
!34680 (merged) introduced a regular migration adding some indices into
ApprovalMergeRules. This model exists on EE, but with single codebase we require for all the migrations to be placed under
The reverse strategy of this migration included the execution of some services that live on EE; to test the different scenarios a spec was created under
spec/migrations: The EE test is skipped if we're running on FOSS mode, otherwise it'll fail because the EE model won't exist.
Given we might encounter this situation in the future, we should define some guidelines on how to deal with this situation.