-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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: wiring up test filters to the Debug page back end #25492
feat: wiring up test filters to the Debug page back end #25492
Conversation
Test summaryRun details
View run in Cypress Dashboard ➡️ Flakiness
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard |
My branch w/ failure: #25475 It worked! I feel silly but how come I don't see this same info reflected in the main page? What branch does this use again? I'm probably forgetting how this works, but it's confusing (and unrelated to this PR): |
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.
This looks good. I tried it out, it works 🆗
@lmiller1990 Can you share a bit more about your comment here: #25492 (comment)
Are you asking why the information on the Debug page is not viewable on the Specs List page? |
User facing changelog
n/a - merging to feature branch
Additional details
When completing the test filtering for the new Debug page in the PR #25265, the backend was stubbed out with test data while the remainder of the work for the cloud integration was being done here: #25316
This PR ties the work from these previous two PRs to enable the test filtering to work for each relevant run used in the new Debug page.
Steps to test
How has the user experience changed?
UI has not changed from the original PR.
PR Tasks
cypress-documentation
?type definitions
?