using Xunit;

// RoomUtils and MatchmakingUtils hold their DbContext factories as process-wide statics, so
// two test classes running at once can serve each other's queries: a class that swaps the
// factory silently points every other in-flight test at an empty database. That made the
// suite pass or fail by scheduling - room-save and role tests failed only in full runs and
// passed on their own. The suite runs in about a second, so serializing it is cheaper than
// the flakiness.
[assembly: CollectionBehavior(DisableTestParallelization = true)]