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
Cannot read property 'signals' of undefined - Windows, Node LTS, latest versions of cypress ad preprocessor #555
Comments
me too, getting the same error after install es lint not sure it related or not. `The following error originated from your test code, not from Cypress.
When Cypress detects uncaught errors originating from your test code it will automatically fail the current test. Cypress could not associate this error to any specific test. We dynamically generated a new test to display this failure.` |
I also face the same issue on mac though |
This error was resolved to me when I set nonGlobalStepDefinitions to true in package.json "cypress-cucumber-preprocessor": { Because of this change, I did moved all step definitions and feature files to their default location. |
I'm also getting this error message on windows
When Cypress detects uncaught errors originating from your test code it will automatically fail the current test. Cypress could not associate this error to any specific test. We dynamically generated a new test to display this failure. my nonGlobalStepDefinitions is set to True "cypress-cucumber-preprocessor": { |
Have you resolved this? |
My friends, I had the same problem, in my case I use cypress with cucumber, I believe you also use it, strangely it was created in a steps file a line automatically 'import cypress from "cypress";' |
Remove |
Removing |
dis you solve the problem? |
Due to personal reasons, the previous maintainers of this package are stepping down and handing the reigns over to me, a long-time contributor to the project and a user of it myself. This is a responsibility I'm very excited about. Furthermore, I'd like to thank @lgandecki ++ for all the work that they've done so far. Read more about the transfer of ownership here. The repository has however moved and all outstanding issues are being closed. This is not a reflection of the perceived importance of your reported issue. However, if after upgrading to the new version, you still find there to be an issue, feel free to open up another ticket or comment below. Please make sure to read CONTRIBUTING.md before doing so. |
On windows, with latest version, tests are failing because of the error in the title
Current behavior
When Cypress detects uncaught errors originating from your test code it will automatically fail the current test.
Cypress could not associate this error to any specific test.
We dynamically generated a new test to display this failure.
at normalizeSignal (http://localhost:3006/__cypress/tests?p=cypress\integration\features\game.feature:65568:1)
at Array.map ()
at getSignals (http://localhost:3006/__cypress/tests?p=cypress\integration\features\game.feature:65548:53)
at getSignalsByName (http://localhost:3006/__cypress/tests?p=cypress\integration\features\game.feature:65455:38)
at Object.501../realtime.js (http://localhost:3006/__cypress/tests?p=cypress\integration\features\game.feature:65469:21)
at o (http://localhost:3006/__cypress/tests?p=cypress\integration\features\game.feature:1:265)
at eval (http://localhost:3006/__cypress/tests?p=cypress\integration\features\game.feature:1:316)
at Object.495.human-signals (http://localhost:3006/__cypress/tests?p=cypress\integration\features\game.feature:64771:25)
at o (http://localhost:3006/__cypress/tests?p=cypress\integration\features\game.feature:1:265)
at eval (http://localhost:3006/__cypress/tests?p=cypress\integration\features\game.feature:1:316)
Desired behavior
Tests should run, fail or success status are not important. I'm using a really basic test on the line 'i can open google'. Even running only the 'Given' bit gives the same result, cypress open or cypress run ( electron and google) gives the same result.
Running through npx or package script is the same
game.spec.js
game.feature
Versions
I saw there are several bugs online for human-signal on windows. That may be the cause ... but could not debug it further, apologies.
The text was updated successfully, but these errors were encountered: