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

Cypress only runs the first test in the test suite and does not proceed further #29494

Closed
sambit-senapati opened this issue May 9, 2024 · 5 comments

Comments

@sambit-senapati
Copy link

sambit-senapati commented May 9, 2024

Current behavior

Cypress runs only the first test in the test suite and does not run the rest of the tests (the time keeps going but it doesn't proceed to the next test).

Example spec:

describe('Create Tests', () => {
  context('Submitting form', () => {
     beforeEach(() => {
      cy.login(testMainUserCreds.username, testMainUserCreds.password)
    })
    it('test case 1', () => {}
    it('test case 2', () => {
  }
 }

I have verified the test suite by running in my colleagues laptop and it runs all of the test suite but the same test suite does not run fully for me

Below steps have been performed,

  • cleared cookies
  • re-installed cypress

Desired behavior

Cypress should run all of the tests in the test suite

Test code to reproduce

describe('Create Tests', () => {
  context('Submitting form', () => {
     beforeEach(() => {
      cy.login(testMainUserCreds.username, testMainUserCreds.password)
    })
    it('test case 1', () => {}
    it('test case 2', () => {
  }
 }
`
Screenshot 2024-05-09 at 3 34 08 PM

Cypress Version

13.6.4

Node version

v18.14.0

Operating System

macOS 14.1.1

Debug Logs

No response

Other

No response

@jennifer-shehane
Copy link
Member

@sambit-senapati Could you please update to the latest Cypress and try rerunning? We did have an issue with this in a previous version that we fixed.

@jennifer-shehane jennifer-shehane added the stage: awaiting response Potential fix was proposed; awaiting response label May 9, 2024
@sambit-senapati
Copy link
Author

@sambit-senapati Could you please update to the latest Cypress and try rerunning? We did have an issue with this in a previous version that we fixed.

sure, will update and let you know, thanks

@sambit-senapati
Copy link
Author

@sambit-senapati Could you please update to the latest Cypress and try rerunning? We did have an issue with this in a previous version that we fixed.

Hey @jennifer-shehane , upgrading to the latest version fixed the issue, thanks

@sk15000
Copy link

sk15000 commented May 15, 2024

@jennifer-shehane for me it is still reproducible:

I am getting the following error, when running the tests through Bitbucket pipeline on Electron, Chrome, Edge, all Cypress versions above 13.3.1 headless. Tried different Docker images as well.

Only the first one or 2 tests are running, and then it stops.

CypressError: Timed out after waiting `60000ms` for your remote page to load.
Your page did not fire its `load` event within `60000ms`.
You can try increasing the `pageLoadTimeout` value in `cypress.config.js` to wait longer.
Browsers will not fire the `load` event until all stylesheets and scripts are done downloading.
When this `load` event occurs, Cypress will continue running commands.

Example not working config (Bitbucket + locally) headless:
│ Cypress: from 13.3.2 to 13.9.0 │
│ Browser: Chrome 114 (headless) │
│ Node Version: v18.16.0 (/usr/local/bin/node)

Example working config (headless)
│ Cypress: 13.3.1 │
│ Browser: Chrome 124 (headless) │
│ Node Version: v20.12.2 (/usr/local/bin/node)

  • But when it runs locally, it has issues with the service workers, so I have to unregister the manually each time.
  • Every other Cypress version after this is not working with the headless Chrome

@jennifer-shehane
Copy link
Member

@sk15000 Please open a new issue with a reproducible example. The issue you're describing is different from the original one posted here.

@jennifer-shehane jennifer-shehane closed this as not planned Won't fix, can't repro, duplicate, stale May 20, 2024
@jennifer-shehane jennifer-shehane removed the stage: awaiting response Potential fix was proposed; awaiting response label May 20, 2024
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