Replies: 8 comments 18 replies
-
Hi, I loved the new debug functionality, however in the local Cypres App only the last execution of the Cypress Cloud is displayed, in my case I run the tests in parallel and I cannot see all the errors in the debug page. |
Beta Was this translation helpful? Give feedback.
-
Hi @pstakoun , I have just added tag "--group daily" and it's failing on the bibucket run, only one rundom command is executing without teardown error. Rest of the runs have the following error message: Any idea ? |
Beta Was this translation helpful? Give feedback.
-
In case it helps someone else: I had to disable the Brave browser shield protection to be able to login into Cypress Cloud & link it to the local app: Without this, I could login but it never went back to the app. |
Beta Was this translation helpful? Give feedback.
-
Agreed with what @lucasdonato mentioned, I'd like to have an option to debug previous run. We do run multiple different suites from single branch during the day, so I would like to be able to choose specific run to debug. |
Beta Was this translation helpful? Give feedback.
-
If login process in google is possible by script like-> describe('Login to Gmail', () => { Will be helpful for us. In selenium it is easy to login in google through the script. But in cypress it is difficult to do google authentication, which is difficult to understand. |
Beta Was this translation helpful? Give feedback.
-
Keen to use this feature but it doesn't appear to work with the Cypress CircleCI Orb where you have multiple parallel stages with unique group names. For example, circleCI config using the official Cypress Orb:
Say 1 test fails for Chrome, but Firefox all passes and finishes last, you will only see the last result in the debug tab and it will show that all tests passed (because it will be the firefox group) Is this a known issue? Any fix? |
Beta Was this translation helpful? Give feedback.
-
Further update: we actually need to use a unique So I think this debug feature need some additional work to allow us to see the history of multiple groups of tests per a branch run. At the moment, it only shows the last one to complete. |
Beta Was this translation helpful? Give feedback.
-
Hey, it's looks good and thanks for adding ability to select previous runs. One more thing I'd find useful is to add button to rerun full .spec next to 'Run failures' button. Usually, when debugging tests we rerun full spec file. |
Beta Was this translation helpful? Give feedback.
-
Today, with the release of Cypress 12.5.0, we are excited to introduce a game-changing Cloud workflow to Cypress, that allows you to easily debug failed CI test runs right from your local app. With the new Debug page, you can review, rerun, and debug failed CI test runs that are recorded to Cypress Cloud – all without leaving the comfort of your local Cypress app.
We encourage you to provide any feedback that you may have, as we are actively iterating on and improving this feature. Please use this thread to provide feedback, request features, or just comment on the new Debug page in general.
If you have a larger bug to report, please file a dedicated issue.
Beta Was this translation helpful? Give feedback.
All reactions