-
Notifications
You must be signed in to change notification settings - Fork 5
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
TESTING: Test API endpoints #66
Comments
After trying to setup mocha and chai for two days, I concluded that it would be easier to use the already installed testing module AVA. The two main reasons are that: 1- It would be more time efficient since AVA is already set-up and there are examples on MERN 2- It would be less heavy on the server |
Also test |
Not goal of the current sprint. |
@pbgnz why is this no longer a goal? We require tests in order to close user stories. |
@jacobrs the back-end is being tested using other tools at the moment. I wanted to prioritize the chat for this spring. So, me and Phil decided to meet this Friday after the tutorial and finish all the back-end tasks. So if everything goes according to plan, I will be working on finishing the tests by next week or so. Before the list increases lol. |
This will be done this sprint. Phil can write the tests for his endpoints in this issue. |
Cannot "mock" login for testing. Therefore, cannot test the authenticated endpoints. |
#66 adding mongod to travis in services
#66 Tests for non authenticated endpoints
Task Description
The User API endpoints have been created and merged in issues #20 and #54. However, there are no unit tests done on the back-end.
Task Breakdown
This issue is divided in two parts:
Setup mocha and chai for the back-end testing
Test the User API endpoint
Test the User authenticate
/me
endpointTest the User logout
/logout
endpointTest the StudyGroup API endpoint
Test the Chat Api and related enpoints
Agile Information
Risk: low
Estimated time: 3hrs
The text was updated successfully, but these errors were encountered: