-
Notifications
You must be signed in to change notification settings - Fork 36
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: migrate to node test runner #690
Conversation
No linked issues found. Please add the corresponding issues in the pull request description. |
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.
I'd take the chance to migrate to Node's mocks as well instead of sinon
Is it something I can do in another PR? |
.gitignore
Outdated
@@ -3,3 +3,4 @@ node_modules/ | |||
.idea | |||
.nyc_output |
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.
do we still need this exclusion?
test/mapUpdateType.test.js
Outdated
t.equal(mapUpdateType('bad_input'), updateTypes.any) | ||
t.equal(mapUpdateType(), updateTypes.any) | ||
t.equal(mapUpdateType('any'), updateTypes.any) | ||
t.assert.deepStrictEqual(mapUpdateType('major'), updateTypes.major) |
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.
do we need the deep part when comparing simple values?
I'm ok with this, sure 👌 |
Checklist
npm run test
andnpm run benchmark
and the Code of conduct