#80 Study Group API

[pbgnz]

Description

This PR allows the front-end to:
1- create, get and delete study groups
2- allow users to join and/or leave study groups

Breakdown

StudyGroups

• Created a new model for study groups
• Created the GET, POST, DELETE endpoints for the study groups
• Created the controller and routes for the study groups

User

• Modified the user model and added a studyGroup field array
• Created the controllers to handle the study groups

Testing

The endpoints were manually tested using postman (See comment below).
AVA tests will be completed in #66

[pbgnz]

The manual testing of the endpoints was done using POSTMAN.

Procedure:

StudyGroups

• 1. Created a study group using the POST endpoint (Screenshot 1)
• 2. Fetched that study group using GET by guid endpoint and verified contents were correct.
• 3. Fetched all study groups using the GET end point and made sure the newly created group was in the list of all study groups (Screenshot 2)
• 4. Deleted the newly created study group using the DELETE endpoint
• 5. Fetched all study groups using the GET end point and made sure the created group in step 1 was properly deleted

User

• 1. A user joins a study group by using the PUT /api/users/:cuid/studyGroup endpoint (Screenshot 3)
• 2. Used the user GET endpoint to verify the study group was successfully added.
• 3. Used the DELETE api/users/:cuid/studyGroup endpoint to delete the study group from the user list.
• 4. Used the user GET endpoint to verify the study group was propoperly deleted.

Screenshot 1: create study group:

Screenshot 2: get study groups:

Screenshot 3: user joins study group:

[jacobrs]

Looks good to me as a first backend implementation!

[Philippe229]

@pbgnz and I went over his code today. Looks good to me.

[Philippe229]

Approved. Conflicts need to be resolved however