-
Notifications
You must be signed in to change notification settings - Fork 0
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
Use Node.js test runner #44
Conversation
# Conflicts: # package.json # yarn.lock
# Conflicts: # .github/workflows/ci-monolib.yml # package.json # yarn.lock
the passes make me think you figured the mocking part out is that correct? If so i'm open to merging the node test runner once the conflict has been resolved 👌 |
I did not figure it out yet, the tests for |
@aduh95 do you have time next week to pair on this? Tuesday would be most convenient on my side, any time is good, does that work for you? |
Sure let's do tuesday 10am? |
Ok, sounds good 👍 |
Co-authored-by: Antoine du Hamel <[email protected]>
# Conflicts: # .eslintrc.js # package.json # packages/prd/src/prd.test.ts # packages/prettier-bytes/src/prettierBytes.ts # packages/trigger-pager/src/triggerPager.test.ts # tsconfig.json # yarn.lock
# Conflicts: # .github/workflows/ci-monolib.yml # package.json # packages/enrich-tweet/src/enrichTweet.test.ts # tsconfig.json # yarn.lock
Cool, thanks for cleaning up this repo both!! |
Took an hour and had some fun converting the test suite here to
node:test
. The only one I'm having trouble with (mocking the pagerduty import in particular) istriggerPager.test.ts
. @aduh95 think you could take a look at that?