Context
We implemented a lot of changes to improve performance on the Cypress e2e tests in Cite including running them in parallel. See T424334: Cypress vs. Selenium Performance and T414556: Investigate if Cypress tests can run faster in CI. These changes introduced a regression for Citoid that uses a different setup CI see T425847: Citoid selenium tests are failing.
Issues
- With the fix implemented to solve the latter we're having issues running the test in parallel seemingly due to race conditions when setting up the cite-tool-definition.json on each spec.
- If cite-tool-definition.json is not setup Citoid does not apply it's UI changes to VE even if the extension is loaded.
- We cannot guarantee if cite-tool-definition.json is created already or not when one spec creates it but another assumes it's not there.
Possible solutions
- Disable parallelization ( for now )
- Find a better way to tell Cypress which UI to expect depending on a combination of Citoid being loaded and the cite-tool-definition.json created
- Move e2e test demonstrating the essential Citoid behavior into Citoid and make sure "pure" Cite tests are not run with a Citoid setup