I don't see why that is required. All we need is an existing RepoProfileApplicability object pointing to a profile that does not exist to verify the fix. If we regenerated applicability for the consumer, we would have an additional RepoProfileApplicability object pointing to the existing latest profile (which is a normal case) and is getting tested by earlier tests anyway.