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

misc: remove New badge for debug page navigation icon #25992

Merged
merged 3 commits into from
Mar 3, 2023

Conversation

astone123
Copy link
Contributor

Additional details

This PR removes the "New" badge from the debug page navigation icon, both the full icon and the "dot" collapsed icon.

Steps to test

Open a project in Cypress and verify the following

  • If you are not logged into Cloud and/or you don't have a project connected, you do not see the "New" badge on the navigation icon for the debug page
  • The other badges on the navigation icon still work as intended (green "0" badge, red "x number of tests" badge)

How has the user experience changed?

See the Percy build

PR Tasks

@astone123 astone123 self-assigned this Mar 1, 2023
@cypress
Copy link

cypress bot commented Mar 1, 2023

24 flaky tests on run #44521 ↗︎

0 26866 1281 0 Flakiness 24

Details:

Merge branch 'develop' of github.com:cypress-io/cypress into remove-debug-new-ba...
Project: cypress Commit: 7c0087bdc8
Status: Passed Duration: 19:20 💡
Started: Mar 3, 2023 6:40 PM Ended: Mar 3, 2023 7:00 PM
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
Flakiness  create-from-component.cy.ts • 2 flaky tests • app-e2e

View Output Video

Test Artifacts
... > runs generated spec Output Screenshots Video
... > runs generated spec Output Screenshots Video
Flakiness  specs_list_latest_runs.cy.ts • 1 flaky test • app-e2e

View Output Video

Test Artifacts
App/Cloud Integration - Latest runs and Average duration > when no runs are recorded > shows placeholders for all visible specs Output Screenshots Video
Flakiness  cypress-in-cypress-component.cy.ts • 1 flaky test • app-e2e

View Output Video

Test Artifacts
Cypress In Cypress CT > default config > redirects to the specs list with error if a spec is not found Output Screenshots Video
Flakiness  cypress-origin-communicator.cy.ts • 1 flaky test • app-e2e

View Output Video

Test Artifacts
Cypress In Cypress Origin Communicator > cy.origin passivity with app interactions > passes upon test reload mid test execution Output Screenshots Video

The first 5 flaky specs are shown, see all 12 specs in Cypress Cloud.

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

Copy link
Contributor

@mike-plummer mike-plummer left a comment

Choose a reason for hiding this comment

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

LGTM

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 like you got everything

@marktnoonan
Copy link
Contributor

I was having trouble seeing new runs show up but it seems unrelated to this branch, will post confirmation shortly.

Copy link
Contributor

@marktnoonan marktnoonan left a comment

Choose a reason for hiding this comment

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

I think I might have had the wrong record key or something in my testing, all good.

@@ -178,18 +177,13 @@ watchEffect(() => {
return
}

const showNewBadge = isAllowedFeature('debugNewBadge', loginConnectStore)
const newBadge: Badge = { value: t('sidebar.debug.new'), status: 'success', label: t('sidebar.debug.debugFeature') }

if (props.gql?.currentProject?.cloudProject?.__typename === 'CloudProject'
&& props.gql.currentProject.cloudProject.runByNumber
&& props.online
) {
const { status, totalFailed } = props.gql.currentProject.cloudProject.runByNumber || {}

if (status === 'NOTESTS' || status === 'RUNNING') {
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need the empty if here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think so, because otherwise we'll hit this code block for the NOTESTS and RUNNING statuses

setDebugBadge({ value: countToDisplay, status: 'error', label: errorLabel })

Which I don't think we want

@astone123 astone123 merged commit e459591 into develop Mar 3, 2023
@astone123 astone123 deleted the remove-debug-new-badge branch March 3, 2023 20:46
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.

Remove "New" badge in sidebar for Debug page
6 participants