Skip to content
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: display a limit warning on the run navigation component when there are 100 total runs #26523

Merged
merged 7 commits into from
Apr 18, 2023

Conversation

astone123
Copy link
Contributor

Additional details

When we implemented run navigation for the debug page, we missed a requirement to display a message when the number of runs is being limited due to being over 100 total across commits.

This PR adds a message to the bottom of the run navigation list that warns the user that they are not seeing all of the runs, and then links to the project in Cypress Cloud for them to view all of the runs that aren't shown in-app.

Since we limit the graphql query to 100 runs, we will display the message when there are exactly 100 runs returned from the query.

Steps to test

Take a look at the tests that I wrote as well as the Percy snapshots. You can also open a project with 100 or more relevant runs on the debug page and verify that the message appears. I used the react-vite-ts example project to test this manually. Recorded over 100 runs to my production test organization and viewed them in the debug page.

How has the user experience changed?

Screenshot 2023-04-17 at 2 44 31 PM

PR Tasks

@astone123 astone123 self-assigned this Apr 17, 2023
</ul>
</div>
<div
v-if="runs.length === 100"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We limit this query to 100 runs, so if we have exactly 100 runs, then we're either at or over the limit, so display the message.

@astone123 astone123 requested review from warrensplayer and a team April 17, 2023 20:51
@cypress
Copy link

cypress bot commented Apr 17, 2023

4 flaky tests on run #45652 ↗︎

0 5193 77 0 Flakiness 4

Details:

fix tests
Project: cypress Commit: 9187ccb11f
Status: Passed Duration: 13:01 💡
Started: Apr 18, 2023 7:32 PM Ended: Apr 18, 2023 7:45 PM
Flakiness  e2e/origin/commands/navigation.cy.ts • 1 flaky test • 5x-driver-electron

View Output Video

Test Artifacts
cy.origin navigation > #consoleProps > .go() Output Video
Flakiness  cypress/cypress.cy.js • 3 flaky tests • 5x-driver-electron

View Output Video

Test Artifacts
... > correctly returns currentRetry Output Video
... > correctly returns currentRetry Output Video
... > correctly returns currentRetry Output Video

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.

Copy link
Contributor

@lmiller1990 lmiller1990 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code looks good, I did not thoroughly test it yet, I'll do this tomorrow. The changes seem pretty straight forward, I'm confident enough to give this a tentative ✅ .

packages/app/src/debug/DebugRunNavigation.cy.tsx Outdated Show resolved Hide resolved
packages/app/src/debug/DebugRunNavigation.cy.tsx Outdated Show resolved Hide resolved
Copy link
Contributor

@warrensplayer warrensplayer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall functionality looks great. Just need to change where the URL comes from. The App can not assume that the Cloud URLS will keep their current format, but instead use the URLs as provided.

packages/app/src/debug/DebugRunNavigationLimitMessage.vue Outdated Show resolved Hide resolved
Copy link
Contributor

@warrensplayer warrensplayer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good after the tests pass!

@astone123 astone123 merged commit 45ca2fa into develop Apr 18, 2023
@astone123 astone123 deleted the debug-run-navigation-limit branch April 18, 2023 19:48
astone123 added a commit to kgroat/cypress that referenced this pull request Apr 19, 2023
tgriesser added a commit that referenced this pull request May 3, 2023
* feat/protocol:
  refactor: migrate from windi to tailwind (#26516)
  chore: update v8 generation vars so that from scratch depends implies updating the metafile (#26472)
  chore: Update Vite to 4.3.0 (#26553)
  fix: unify cdp approach to fix devtools in electron (#26573)
  dependency(deps): update dependency deps-ok to v1.4.1 🌟 (#26612)
  chore: update 12.11.0 release date (#26587)
  chore: 12.11.0 release (#26582)
  chore: implement experimental ESM stub/spy for Vite (#26536)
  chore: try triggering mouseleave on buttons to ensure that tooltips aren't showing (#26524)
  chore: add support for Angular 16 (#26052)
  chore: upgrade Vue to 3.2.47 (#26555)
  chore: Update v8 snapshot cache (#26537)
  chore: add missing utm parameters for cloud links to Debug page (#26556)
  chore: update stalebot to respect new labels and up process rate (#26552)
  fix: don't display run passing status if Cloud org is over run limit (#26533)
  chore: update vm2 to 3.9.17 (#26534)
  feat: display a limit warning on the run navigation component when there are 100 total runs (#26523)
  chore: Update v8 snapshot cache (#26476)
  chore: upgrade vm2 (#26495)
  fix: Treat Video compression 0 as false.  (#26503)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Debug Run Navigation - More than 100 runs message
3 participants