-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Conversation
24 flaky tests on run #44521 ↗︎Details:
|
Test | Artifacts | |
---|---|---|
... > correctly returns currentRetry |
Output
Video
|
|
... > correctly returns currentRetry |
Output
Video
|
|
... > correctly returns currentRetry |
Output
Video
|
create-from-component.cy.ts • 2 flaky tests • app-e2e
Test | Artifacts | |
---|---|---|
... > runs generated spec |
Output
Screenshots
Video
|
|
... > runs generated spec |
Output
Screenshots
Video
|
specs_list_latest_runs.cy.ts • 1 flaky test • app-e2e
Test | Artifacts | |
---|---|---|
App/Cloud Integration - Latest runs and Average duration > when no runs are recorded > shows placeholders for all visible specs |
Output
Screenshots
Video
|
cypress-in-cypress-component.cy.ts • 1 flaky test • app-e2e
Test | Artifacts | |
---|---|---|
Cypress In Cypress CT > default config > redirects to the specs list with error if a spec is not found |
Output
Screenshots
Video
|
cypress-origin-communicator.cy.ts • 1 flaky test • app-e2e
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.
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.
LGTM
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.
Looks like you got everything
I was having trouble seeing new runs show up but it seems unrelated to this branch, will post confirmation shortly. |
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 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') { |
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.
Do we need the empty if
here?
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 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
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
How has the user experience changed?
See the Percy build
PR Tasks
cypress-documentation
?type definitions
?