-
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
web application doesn't load correctly with Cypress #4042
Comments
Hey @pinko2512 are there any errors displaying within the Cypress Test Runner? Could you print those? Unfortunately, this will be quite difficult to track down without being able to reproduce on our end, but any more information you can provide, screenshots/videos may be helpful. |
We fixed the issue. The problem was that when we opened first The same file run on the standalone Chrome was loaded correctly, so it had to be issue with Cypress encoding. After some googling we found that Cypress settings has a default settings with this property: https://on.cypress.io/configuration#modifyObstructiveCode After setting it to |
@pinko2512 Nice investigating. Could you provide the original function code as it appeared in normal Chrome versus the function code that displays within the Cypress browser when There should have been something surrounding this code related to We certainly don't intend to create any malformed tokens like this. |
@pinko2512 Any update on this? |
Unfortunately we have to close this issue due to inactivity. Please comment if there is new information to provide concerning the original issue and we can reopen. |
Hello Jennifer. I'm new in cypress and I'm getting this error too, but I don't identify how can localice the "wrong" code. The Dev team made some changes last week and I started to get this error today that I have updated project, and I don't know how to tell them what search for and adjust. If I add ("modifyObstructiveCode": false) to the config, my script runs but i don't know if this can affect other scripts. |
chore(nx): move some schematics into @nrwl/angular chore(nx): add e2e test feat(nx): add storybook schematics and builder test: Add tests test: remove test chore: Move some schematics into @nrwl/angular test: fix tests chore: Add e2e test chore: Bump storybook versions chore: createTestUiLib takes a libName argument chore: configs extend root config fix: Remove custom scss loader feat: add storybook builder fix: generate documentation and fix linting chore: Builder tests passing fix(nx): configuration schematic can run multiple times feat(nx): component story format docs(nx): update storybook docs fix(nx): pin core-js dev dependency to ^2.6.9 chore(nx): fix formatting chore(nx): match core-js version for web/storybook chore(nx): remove storybook's angular dependencies chore(nx): modifyObstructiveCode to false in cypress.json See: cypress-io/cypress#4042 (comment) chore(nx): storybook tests --no-interactive chore(nx): add storybook to e2e tests chore(nx): reorder e2e tests
chore(nx): move some schematics into @nrwl/angular chore(nx): add e2e test feat(nx): add storybook schematics and builder test: Add tests test: remove test chore: Move some schematics into @nrwl/angular test: fix tests chore: Add e2e test chore: Bump storybook versions chore: createTestUiLib takes a libName argument chore: configs extend root config fix: Remove custom scss loader feat: add storybook builder fix: generate documentation and fix linting chore: Builder tests passing fix(nx): configuration schematic can run multiple times feat(nx): component story format docs(nx): update storybook docs fix(nx): pin core-js dev dependency to ^2.6.9 chore(nx): fix formatting chore(nx): match core-js version for web/storybook chore(nx): remove storybook's angular dependencies chore(nx): modifyObstructiveCode to false in cypress.json See: cypress-io/cypress#4042 (comment) chore(nx): storybook tests --no-interactive chore(nx): add storybook to e2e tests chore(nx): reorder e2e tests
chore(nx): move some schematics into @nrwl/angular chore(nx): add e2e test feat(nx): add storybook schematics and builder test: Add tests test: remove test chore: Move some schematics into @nrwl/angular test: fix tests chore: Add e2e test chore: Bump storybook versions chore: createTestUiLib takes a libName argument chore: configs extend root config fix: Remove custom scss loader feat: add storybook builder fix: generate documentation and fix linting chore: Builder tests passing fix(nx): configuration schematic can run multiple times feat(nx): component story format docs(nx): update storybook docs fix(nx): pin core-js dev dependency to ^2.6.9 chore(nx): fix formatting chore(nx): match core-js version for web/storybook chore(nx): remove storybook's angular dependencies chore(nx): modifyObstructiveCode to false in cypress.json See: cypress-io/cypress#4042 (comment) chore(nx): storybook tests --no-interactive chore(nx): add storybook to e2e tests chore(nx): reorder e2e tests
chore(nx): move some schematics into @nrwl/angular chore(nx): add e2e test feat(nx): add storybook schematics and builder test: Add tests test: remove test chore: Move some schematics into @nrwl/angular test: fix tests chore: Add e2e test chore: Bump storybook versions chore: createTestUiLib takes a libName argument chore: configs extend root config fix: Remove custom scss loader feat: add storybook builder fix: generate documentation and fix linting chore: Builder tests passing fix(nx): configuration schematic can run multiple times feat(nx): component story format docs(nx): update storybook docs fix(nx): pin core-js dev dependency to ^2.6.9 chore(nx): fix formatting chore(nx): match core-js version for web/storybook chore(nx): remove storybook's angular dependencies chore(nx): modifyObstructiveCode to false in cypress.json See: cypress-io/cypress#4042 (comment) chore(nx): storybook tests --no-interactive chore(nx): add storybook to e2e tests chore(nx): reorder e2e tests
I tried adding |
Yes, If you're experiencing a bug similar to this in Cypress, please open a new issue with a fully reproducible example that we can run. There may be a specific edge case with the issue that we need more detail to fix. |
My team is working on a web application and we decided to use Cypress for automated tests. Problem is, when we run these tests, they only get past login screen. Home screen doesn't load correctly. This happens ONLY in Chrome driven by Cypress and Electron driven by Cypress. In normal Chrome the application runs without errors.
Current behavior:
When running Cypress tests, web application doesn't load correctly and console displays these errors on home screen:
Desired behavior:
Behaviour should be the same in standalone Chrome and Chrome driven by Cypress (and Electron).
Versions
Windows 10
Cypress 3.2.0,
Chrome 74, Electron 59
If somebody knows what's happening and how can it be fixed, please let me know. Thank you
The text was updated successfully, but these errors were encountered: