Currently there are two test classes that try to assert the content of the Designer project bundle after running a JSF migration upgrade: ContentViewUpgradeTest and UserActionUpgradeTest. These had to be disabled, due to the pseudo-random result of the test.
It’s not confirmed, but we believe that this behaviour was caused due to the different order of the contributions on the project bundle. If this is true, there are two options:
1. Ensure that the content of bundle is generated following a deterministic order, regardless of which contribution is added first.
2. When comparing the generated bundles, instead of validating the content of the files as a whole, assert the number of contributions in the bundles and if each one of the expected contributions exists, with the expected parameters.