Flaky tests: Launchpad: Setup Project (project-setup.cy.ts)

[jennifer-shehane]

What would you like?

We have some tests that continues the flakiest tests in our suite. You can see examples of this in several tests:

• takes the user to first step of ct setup when switching from app
• skips the setup page when choosing e2e tests to run
• shows the configuration setup page when selecting e2e tests
• can reconfigure config after CT has been set up
• can skip setup CT testing for an E2E project
• opens docs link in the default browser
• skips the setup steps when choosing component tests to run

It will most often exhibit as a loading spinner never going away after opening a project and visiting the launchpad, when the tests specifically are testing a flow where e2e or ct tests have already been chosen and configured.

expected <svg.spinner> not to exist in the DOM

In these situations, when comparing a passing and failing Test Replay, you can see one critical difference.

• When this test passes, the response body of POST /__launchpad/graphql/query-MainLaunchpadQuery has data.currentProject.isCTConfigured or data.currentProject.isE@EConfigured as true (depending on the testing flow you were testing.
• When this test fails, the response body of POST /__launchpad/graphql/query-MainLaunchpadQuery has data.currentProject.isCTConfigured and data.currentProject.isE@EConfigured as both false.

Passes

Fails

The Launchpad is not coded to expect a situation where the 'currentTestingType' shows a specific testing type, yet the isE2EConfigured or isCTConfigured is not true as it should be, so it just sits forever in this loading state.

I was unable to determine if this was an issue with how we mock our data for the tests or an actual issue in our App. This needs to be investigated.

Why is this needed?

No response

Other

No response