quanalogy / cloudscrum Goto Github PK

How do we want files to be named? For instance the tests of the user model and user controller. Is it worth it to have extremely long names such as controller.user.patch.ts?

We can patch an users password without authentication, because of path to /users/ instead of eg home

Seems like the patch request of password change is accepted, all the way, but it does not store the new password. (and yes it does fulfill the regex for create pw)

when creating a new user and when changing password at the userpanel, we need to add another input field and check if the two passwords match!

Currently, some of the testing is done multiple times in different aspects. For instance, both in the end to end testing and in the individual unit tests. To speed up the entire test suite, we wish to reduce this.

• Scrap old testing
• Create unit tests for the models
• Create unit tests for the controllers, with mock models
• Create end to end tests, with mock controllers

This is a bottom up testing approach, but with mock objects to speed up the testing process. Especially the bcrypt and database handling are costly and can be avoided in this manner.

Work will be done on the RefactorTesting branch.

Create tests for reading a single and multiple users, and implement them both for end to end and the controller part. Implement the route.