-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
add working wallaby config #3224
Conversation
As discussed at wallabyjs/public#1490 (comment)
😍 awesome, can't wait to try this. thanks @ArtemGovorov |
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.
SPLENDID
// to expose it/describe etc. on the mocha under test | ||
const mochaUnderTest = new (require('./'))(); | ||
mochaUnderTest.suite.emit('pre-require', global, '', mochaUnderTest); | ||
// to make test/node-unit/color.spec.js pass, we need to run mocha in the project's folder context |
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.
@ArtemGovorov how did you figure this out?
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.
Just had been reading mocha source code and discovered it. Wallaby uses mocha a bit differently from how mocha CLI is using mocha :)
Description of the Change
Added Wallaby config file as discussed at wallabyjs/public#1490 (comment).
Alternate Designs
n/a
Why should this be in core?
n/a
Benefits
Mocha contributors who are using Wallaby can continuously run mocha tests.
Possible Drawbacks
n/a
Applicable issues
n/a