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 does not work in airplane mode or without network #4279

Closed
digitaldrummerj opened this issue May 22, 2019 · 2 comments
Closed

Cypress does not work in airplane mode or without network #4279

digitaldrummerj opened this issue May 22, 2019 · 2 comments
Labels
stage: proposal 💡 No work has been done of this issue

Comments

@digitaldrummerj
Copy link

Current behavior:

When trying to run Cypress test without network or in airplane mode, the test window just shows a blank solid white screen and never brings up the tests. The website works just fine locally without network when I run everything locally.

airplane

Desired behavior:

Successfully launch and run the tests even without network or in airplane mode.

cypress success

Steps to reproduce: (app code and test code)

  1. Clone https://github.com/digitaldrummerj/angular-tutorial-code
  2. cd into angular-tutorial-code
  3. Checkout branch chapter-ui-tests (git checkout chapter-ui-tests)
  4. run npm install
  5. install Angular CLI (npm install -g @angular/cli)
  6. run ng serve
  7. run npx cypress open
  8. click the "run all specs" button
  9. all test should pass
  10. close Cypress Chrome window
  11. disconnect network or turn on airplane mode
  12. click the "run all specs" button
  13. the Cypress Chrome window should now just be a blank white window

Versions

Windows 10.0.17134
Chrome 74
Cypress 3.2.0

@cypress-bot cypress-bot bot added the stage: proposal 💡 No work has been done of this issue label May 22, 2019
@bahmutov
Copy link
Contributor

@digitaldrummerj can you check v3.4.1 - I think this has been fixed, and your issue is duplicate of #4763

@jennifer-shehane
Copy link
Member

Since this issue hasn't had activity in a while, we'll close the issue until we can confirm this is still happening. Please comment if there is new information to provide concerning the original issue and we'd be happy to reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stage: proposal 💡 No work has been done of this issue
Projects
None yet
Development

No branches or pull requests

3 participants