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

Flaky test: Tests fail in azure devops pipeline #27289

Closed
Abdul-abdulwahab opened this issue Jul 13, 2023 · 1 comment
Closed

Flaky test: Tests fail in azure devops pipeline #27289

Abdul-abdulwahab opened this issue Jul 13, 2023 · 1 comment
Assignees

Comments

@Abdul-abdulwahab
Copy link

Link to Cypress Cloud or CircleCI failure

I have an uncaught error in the app and I was handled the error using below code in e2e.js file

Cypress.on('uncaught:exception', (err, runnable) => {
// returning false here prevents Cypress from
// failing the test

return false
})

Tests are running in test runner or headless mode no issues however when I run same tests in Azure devops pipeline nothing working. see below:

image

Link to failing test in GitHub

I have an uncaught error in the app and I was handled the error using below code in e2e.js file

Cypress.on('uncaught:exception', (err, runnable) => {
// returning false here prevents Cypress from
// failing the test

return false
})

Tests are running in test runner or headless mode no issues however when I run same tests in Azure devops pipeline nothing working. see below:
image

Analysis

Tests are running in test runner or headless mode no issues however when I run same tests in Azure devops pipeline nothing working.

Cypress Version

12.16.0

Other

No response

@Abdul-abdulwahab Abdul-abdulwahab changed the title Flaky test: Tests fail in azo Flaky test: Tests fail in azure devops pipeline Jul 13, 2023
@jennifer-shehane
Copy link
Member

@Abdul-abdulwahab Please try updating to v13+ and using Test Replay in Cypress Cloud to see your run in CI vs local. It’s helpful for debugging flake like this and narrowing down what in your environment may have caused it. If you can narrow this down to a specific bug in Cypress, plz reopen an issue explaining the bug.

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

No branches or pull requests

3 participants