The main duty of `dispatchCustomizationEvents` is to dispatch one, and only one `customization` event by each setting inside the proper entry of a given `variantCustomization` object. In the same way, it is not the goal of the test to rely on `Resources.load` or `getMccMnc()` methods. So, there are two points of improvement here:

1. Craft a custom `variantCustomization` object to pass to `dispatchCustomizationEvents()` method. Do not rely on `Resources.load()` nor on `VariantManager.getMccMnc()` please.
2. As you know how many keys you are providing in your test customization object, prepare an event handler which mark as dispatched every setting in your customization object. When all are dispatched, call `done()`.

What do you think?