Description | Points |
---|---|
The game runs according to the specification | 2 |
Can create a new player from the frontend (stored in DB) | 2 |
Can update a player's score from the frontend (updated in DB) | 2 |
Delete a player from the frontend (deleted in DB) | 3 |
Retrieve and display the best player from the DB | 3 |
Retrieve and display all the players from the DB | 3 |
(GET) /players route implementation | 5 |
(POST) /player route implementation | 5 |
(GET) /player/{id} route implementation | 5 |
(PUT) /player/{id} route implementation | 5 |
(DELETE) /player/{id} route implementation | 5 |
(GET) /player/leaders/{id} route implementation | 5 |
DB operations in a separate js file(s) | 5 |
Testing code coverage >=80% | 10 |
End-to-end test #1 | 2 |
End-to-end test #2 | 2 |
End-to-end test #3 | 2 |
Link TravisCI with Github | 4 |
No ESLint error (Airbnb style) | 5 |
Github unit test branch | 1 |
Github end-to-end test branch | 1 |
Github implementation branch | 1 |
Correct branching/merging flow (pull requests) | 2 |
Deployed the application | 15 |
Total | 95 |