Fix mutator ordering issue in apex tests
Previously, the override mutators were being run before the prebuilt mutators that did not match the runtime behavior. This change fixes that ordering. In the process it broke TestApexWithAppImportsPrefer. That test tries to verify that an apex that depends on an android_app will use an android_app_import if that is preferred. Unfortunately, it only worked because of the incorrect order of the mutators. The test worked before this change because the prebuilt mutators were being run after the overridableModuleDepsMutator. That meant that any dependencies added by that mutator onto source modules could be replaced by the PrebuiltPostDepsMutator with the preferred prebuilt module. Switching the order to match the runtime meant that the prebuilt mutators were run before the overrides so never had a chance to replace the dependencies added by the overrides. Bug: 181953909 Bug: 181974714 Test: m nothing Change-Id: Ic98fdc29a63155174a3227e7e918b26f0a8763bb
Loading
Please register or sign in to comment