You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The query used by the Debug page currently pulls back every failed test in the testsForReview field. This could cause a large amount of data to be returned if a failed build has a large amount of failed tests. This state is not very helpful to a developer to debug a large set of failed tests at the same time.
Desired state
In the DebugContainer component, update the query to set the limit value for the testsForReview field to 100.
If the totalFailed count for the CloudRun, is greater than 100, then show a banner at the bottom of the page that says: "Cypress renders up to 100 failed test results * This run has {totalFailed} failed tests * See all test results in Cypress Cloud". The last part should be a link to the run in the Cloud. This link should be the same as the one used in the page header that says "View in Cypress Cloud"
Current state
The query used by the Debug page currently pulls back every failed test in the
testsForReview
field. This could cause a large amount of data to be returned if a failed build has a large amount of failed tests. This state is not very helpful to a developer to debug a large set of failed tests at the same time.Desired state
In the
DebugContainer
component, update the query to set thelimit
value for thetestsForReview
field to 100.If the
totalFailed
count for the CloudRun, is greater than 100, then show a banner at the bottom of the page that says: "Cypress renders up to 100 failed test results * This run has {totalFailed} failed tests * See all test results in Cypress Cloud". The last part should be a link to the run in the Cloud. This link should be the same as the one used in the page header that says "View in Cypress Cloud"Figma: https://www.figma.com/file/PAOozuCxtfetqP8fUVvg0y/branch/QkCp2F69X0qyLo7qnYQ67e/Cypress-App?node-id=21467%3A202325&t=P5M2orPSQj5Xv4IL-1
The text was updated successfully, but these errors were encountered: