-
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
Test: handler-resolver.ts tests + adding tests to github actions workflow #45
Conversation
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.
This looks great, thanks for testing this so thoroughly. I actually didn't write this code, it came with the skeleton, had no idea what it did. Now i do!
src/libs/handler-resolver.test.ts
Outdated
@@ -0,0 +1,63 @@ | |||
import { handlerPath } from './handler-resolver'; | |||
|
|||
describe('handlerPath success cases', () => { |
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.
Hmm I sort of feel like structurally, it makes more sense to have 1 describe block for the "handlerPath function" and then nested within THAT are 2 different it.each
blocks for success and error. What do you think?
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.
Updated to nest it in a describe block
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.
Wonderful
Added tests for libs/handler-resolver.ts + updated ci.yml to include running tests