Cypress test are failing and not always because of actual broken features

[edwinmp]

Look into why this is happening for and suggest a solution & perhaps a plan for how we can better structure our e2e tests to only break for proper issues.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[edwinmp]

I'm increasing the priority of this as it's falling further behind on our list of technical debt tickets.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[APIYOJENNIFER]

The Cypress tests are failing intermittently due to the following issues:

• Timeout errors due to the cypress commands running before the page has fully loaded.
• Delays in loading content, which I suspect are due to large file sizes.
• Timeout errors due to slow response when making API requests.

Suggested solutions:

• Intercept all network requests and wait until it's complete before running the next cypress commands.
• Add delays where cy.type() is being used.

[ThatcherK]

@APIYOJENNIFER Way forward on your findings

• Find all the network requests that are causing timeouts and intercept them so that all the commands that need to run after them are run after the network call is successful is made.
  This resource might be helpful https://dev.to/m1073496/cypress-and-flaky-tests-how-to-handle-timeout-errors-4ggm

[ThatcherK]

All tests have been fixed apart from the deletes a frozen datasource test under datasources, where fixing the timeout errors exposed an api error that is referenced in this issue #970