-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Test execution freezes with a NodeJS version >= 10.12.0 #52
Comments
I have the same issue. All 10+ versions of node, on Windows, freezes as soon as I run any test similar to this:
@SBoudrias - any thoughts? |
Hi @wictorwilen, We implemented a workaround for this issue in which we evaluated the version of NodeJS before running the tests. before( … ) {
if(semver.gte(process.versions.node, `10.12.0`)) {
run = false;
…
} else {
…
//GENERATOR LOGIC
…
}
}
describe(…) {
if(!run) {
this.skip();
}
…
// TEST LOGIC
…
} If you want to see the entire code, check here. |
Thanks @Batta32 - it's a good workaround, but it would be great to be able to test on LTS versions of node. Node 8 support ends in only 6 months |
Should be fixed with inquirer 7.0.2 |
Related issues: #51, feathers-plus/generator-feathers-plus#103, yeoman/generator#1098
Environment: Windows 10, NodeJS >= 10.12.0, mocha 5.2.0
When testing with the yeoman helper, I discovered that by making several hooks' calls to run the generator with prompts, it locks on the same point.
Example:
This happens using
CMD
andPowerShell
(what is strange is that in each of them, the execution tests are locked in different points). However, usingbash
, the execution tests end successfully.Debugging the tests, I found out that the
prompting
method runs fine and resolves the promise okay.The problem is that the
writing
method never runs at the second time that thehelpers.run
is called inside thebeforeEach
hook.Finally, changing the prompts to arguments was the workaround that I found even though is not the final solution I want (this works in all the environments).
Example:
The text was updated successfully, but these errors were encountered: