-
Notifications
You must be signed in to change notification settings - Fork 173
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
Replace Nodeunit with Mocha #294
Conversation
Hm... The tests are failing because Node.JS 12.17+ is required for Jasmine. |
This reverts commit caccbb8.
I'm sorry @shunkica , I was working on another project that used Jasmine, this org uses Mocha. I've pushed a change to support Mocha. Thank you for your hard work! |
@LoneRifle , this is going to be an ever bigger problem going forward. I suggest that we read this and decide what we'd like to do. I'm all for supporting |
@cjbarth I concur; I took the trouble to look at NodeJS' download metrics. It is worth noting that most downloads in the past two years or so are limited to My only concern is within enterprise organisations, which tend to have very long change management cycles to bring in new software releases and hence a tendency to have very old releases of Node. But considering the number of security vulnerabilities found in older releases, perhaps these organisations would have moved quicker to get to newer ones. |
Reviewing this code is very difficult. I'm going to avoid the rename for the first pass, review it, land it, and then do a file rename. |
For reference, here is the log of tests from
|
You would need something like this to count the number of assertions made Edit:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All the tests look like they were ported without any changes.
No description provided.