-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Implement testing type switch promos #26894
Conversation
5 flaky tests on run #47125 ↗︎
Details:
commands/net_stubbing.cy.ts • 1 flaky test • 5x-driver-electron
e2e/origin/navigation.cy.ts • 1 flaky test • 5x-driver-electron
cypress/cypress.cy.js • 3 flaky tests • 5x-driver-electron
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few comments. Also I'm curious why the snapshot cache files were updated?
@astone123 kitchensink and unit tests are failing due to weird errors related to require & package.json. I ran the snapshot update task just to make sure it wasn't a snapshot mismatch since there are updates to the yarn.lock in this PR |
* Fix issue with yarn.lock * Fix extra padding at bottom of promo * Add tests for utm params * Add test for switching testing type when both configured * Fix changelog version
@astone123 Removed extra padding in latest commit |
@mike-plummer One more minor thing I'm seeing - when I launch a project that has e2e configured but not CT, when the app loads I see the CT promo flash on screen very quickly. Probably not a huge deal, but I imagine we could prevent that from happening for a smoother experience. For example |
@marktnoonan looks good overall, but I'm still seeing this behavior that I mentioned in this comment. Not a huge issue but it would be nice if it was an easy change Edit: Actually what I'm seeing now is that the e2e promo is flashing on screen (which is the testing type that is configured) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just tested again, looks good!
Fixed this issue in 707350f |
I think I still saw the flashing banner bug, but I realized it was another banner. I am unsure if it was introduced here, but I suspect it was not. I'll find out. Here's the bug recorded. It only happens sometimes, the first time you open a project? bug.mov |
The actual feature works great, I tested it out, looks good! |
I re-ran Edit, maybe I'd missed 54cb1a0 where @marktnoonan fixed the issue. It seems fine now! |
I pushed a single commit after getting it all green that removed a superfluous snapshot (this component is captured in several others): 59df96a. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Additional details
A new testing type switcher is being added to the Specs Explorer. It has the following behaviors:
If other testing type is configured
If other testing type is not configured
machine-collect
eventFigma
Note: The following discrepancies with the Figma have been surfaced with design and approved:
Steps to test
How has the user experience changed?
Both testing types configured
CT not configured
E2E not configured
PR Tasks
cypress-documentation
?type definitions
?