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

fix: don't display run passing status if Cloud org is over run limit #26533

Merged
merged 1 commit into from
Apr 19, 2023

Conversation

astone123
Copy link
Contributor

Additional details

When a run's results are hidden because the cloud organization is over its test result limit for the month, we shouldn't show the passing state and should only show the "over limit" message on the debug page for that run. Having both messages on screen doesn't look great and could be confusing.

Steps to test

Check out the test that I wrote. Alternatively, spin up a project and record enough runs to go over your free limit on Cypress Cloud. Verify that when you have a passing run selected that is hidden because you are over the limit, that you don't see the passing message of "Well Done! All your tests passed." on screen, and only see the over limit message.

How has the user experience changed?

Before: look at the attached issue

After:
Screenshot 2023-04-18 at 11 23 20 AM

PR Tasks

@cypress
Copy link

cypress bot commented Apr 18, 2023

6 flaky tests on run #45684 ↗︎

0 5133 137 0 Flakiness 6

Details:

fix: don't display run passing status if Cloud org is over run limit
Project: cypress Commit: 77490fe494
Status: Passed Duration: 12:41 💡
Started: Apr 19, 2023 7:45 PM Ended: Apr 19, 2023 7:58 PM
Flakiness  commands/net_stubbing.cy.ts • 1 flaky test • 5x-driver-firefox

View Output Video

Test Artifacts
network stubbing > intercepting request > can delay and throttle a StaticResponse Output
Flakiness  e2e/origin/commands/navigation.cy.ts • 1 flaky test • 5x-driver-firefox

View Output Video

Test Artifacts
cy.origin navigation > #consoleProps > .go() Output
Flakiness  e2e/origin/commands/assertions.cy.ts • 1 flaky test • 5x-driver-firefox

View Output Video

Test Artifacts
cy.origin assertions > #consoleProps > .should() and .and() Output
Flakiness  cypress/cypress.cy.js • 3 flaky tests • 5x-driver-firefox

View Output Video

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

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

@@ -22,7 +22,7 @@
v-if="['PASSED', 'OVERLIMIT'].includes(status) || isHidden"
class="flex flex-col flex-grow w-full p-12 justify-center items-center align-middle "
>
<DebugPassed v-if="status === 'PASSED'" />
<DebugPassed v-if="status === 'PASSED' && !isHidden" />
Copy link
Contributor

Choose a reason for hiding this comment

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

I tried to take look to find out what constitutes isHidden - looks like this comes from the Cloud, going to assume that this value is correctly calculated (validating it is outside the scope of this repo and PR).

Do you have any context/knowledge of how this is calculated?

Code looks good!

@astone123 astone123 requested a review from a team April 19, 2023 17:59
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. Just one comment to consider for the future.

@@ -22,7 +22,7 @@
v-if="['PASSED', 'OVERLIMIT'].includes(status) || isHidden"
class="flex flex-col flex-grow w-full p-12 justify-center items-center align-middle "
>
<DebugPassed v-if="status === 'PASSED'" />
<DebugPassed v-if="status === 'PASSED' && !isHidden" />
Copy link
Contributor

Choose a reason for hiding this comment

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

You could have switched the order with the DebugOverLimit below and then added a v-else-if="status === 'PASSED'", but this works just fine.

@astone123 astone123 merged commit 4963893 into develop Apr 19, 2023
@astone123 astone123 deleted the debug-passing-over-limit branch April 19, 2023 19:56
ryanthemanuel added a commit that referenced this pull request May 1, 2023
Co-authored-by: Matt Henkes <[email protected]>
Co-authored-by: cypress-bot[bot] <+cypress-bot[bot]@users.noreply.github.com>
Co-authored-by: Ryan Manuel <[email protected]>
Co-authored-by: Leosvel Pérez Espinosa <[email protected]>
Co-authored-by: astone123 <[email protected]>
Co-authored-by: Mark Noonan <[email protected]>
Co-authored-by: Mike Plummer <[email protected]>
Co-authored-by: Mike Plummer <[email protected]>
Co-authored-by: Lachlan Miller <[email protected]>
Co-authored-by: Stokes Player <[email protected]>
Co-authored-by: Stokes Player <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Adam Stone-Lord <[email protected]>
Co-authored-by: Ben M <[email protected]>
Co-authored-by: Jordan <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Barthélémy Ledoux <[email protected]>
fix: Treat Video compression 0 as false.  (#26503)
fix: don't display run passing status if Cloud org is over run limit (#26533)
fix: unify cdp approach to fix devtools in electron (#26573)
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.

Improve/correct Debug Page UI when viewing run with no failures but organization is over the record limit
3 participants