-
Notifications
You must be signed in to change notification settings - Fork 34
Issue #21: Add unit test to authSignupController for existing user scenario #59
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
base: main
Are you sure you want to change the base?
Conversation
…SignupController.test.js for clarity
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.
Looks good to me!
sourabhk25
left a comment
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 PR seems improperly labelled. It does not address #21, instead, #21 seems like a prerequisite for it. #21 simply configures testing to work on the project, it isn't all-encompassing of all-things-testing. However, it does need to be completed and accepted before any other testing code (such as this PR) is committed. Consequently, if this is accepted (either now or in the future), it should be Squashed to replace references to #21 with its real purpose: testing |
4bd9ad5

mainbranchmainalong with a status badge inREADME.md