-
-
Notifications
You must be signed in to change notification settings - Fork 145
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
Write tests for account #12
base: master
Are you sure you want to change the base?
Conversation
cd45b6e
to
9db7fa5
Compare
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.
Looking great here, however, instead of validating the currrent (wrong) behavior, please change the tests to validate the desired behavior as indicated, so that the tests fail and can be fixed.
Note: Do not fix them in this PR please, as that may require those changes to be mirrored to the frontend.
My approach was to not change anything due to the So next steps: I will fix the API first with backend <-> frontend manual tests, then I want to merge that one with correct behavior already on |
Having failing tests is fine, I would merge the PR regardless. |
If it is not blocking anything (like docker build and push, i don't know) then why not |
9db7fa5
to
81a01aa
Compare
81a01aa
to
df971a2
Compare
* skip tests on windows * move db consts at the top of the file * print connection string for debugging * verify future (ideal) status codes&messages instead of the current wrong stuff
df971a2
to
c1d2a44
Compare
please tell me, if you like the approach
tests need a little bit more cleaning and polishing, but i post it early to gather a feedback
i can also test other routes in the future