279 unit tests

[ryankroon00]

closes #279

What is it supposed to do
The pr adds end point tests to the back end

How can we test your branch

• go to the backend folder
• npm i
• npm run reset
• open a new terminal
• npm test

1. General checklist

• [x] a. Tested happy flow.
• [x] b. Tested unhappy flow.
• [x] c. No unexpected exceptions.
• [x] d. No code with high complexity. (Big O)
• [x] e. EOF newline.
• [x] f. No linter warnings or errors.

2. If relevant, front-end checklist

• [ ] a. Responsive. (Desktop all the way to mobile 320px)
• [ ] b. Using SCSS variables where relevant.
• [ ] c. Relevant class names
• [ ] d. No modified global SCSS properties, except if necessary and fully tested the impact.
• [ ] e. Checked caniuse for more modern CSS properties.

3. If relevant, back-end checklist

• [x] a. No unhandled promise rejections.
• [x] b. Seeders still functional.
• [x] c. No primary-key violations.
• [x] d. Normalization, at least 3NF.
• [x] e. Used guards (middleware) where necessary and tested if route is guarded.

4. If relevant, test these browsers

• [x] a. Chrome
• [x] b. Firefox
• [ ] c. Opera
• [ ] d. Edge
• [ ] e. Safari

---

PR Rules
1. Add relevant labels.
2. Select at least two reviewers.
3. Assign all reviewers allowed to merge the branch, including yourself.
4. If relevant to the sprint, put related issue in 'Awaiting Approval' column on project board.
5. Add to the corresponding milestone.

[jerohero]

Looks like mocha wasn't properly added to the package.json. I had to do npm i mocha to be able to run the test.

[AjobK]

Also, fix merge conflicts please :-)