Google Code-in

Prerequisite:

• Have a GitHub account
• Know how to use git
• Setup and run the project on your local development environment

Steps:

• Create a copy of the project into your account GitHub by forking systers/mentorship-backend project.
• Clone the project onto your local development environment.
• [Optional] Create a branch to make your changes.
• Write tests that cover the test cases from this table for the PUT /user/change_password API that don't currently exist.
• Write the following tests that are not in the table:
  • Valid user tries to change password with authentication token missing (FAIL)
  • Valid user tries to change password with authentication token expired (FAIL)
• Commit your change using our Commit message Style Guide.
• Submit a Pull Request, targeting gci-dev branch, following the template provided in the description (with reference to issue #308).

Resources:

• If you need help or get lost, post a "New topic" in the coding-backend-tasks stream.
• Pull request template at this link.
• Commit message Style Guide can be found here.
• How to fork, clone and setup remotes the project into your account wiki page can be found here.
• Quality Assurance test cases for Change Password API table.

Work Submission:

Submit a link to Pull Request (PR) created with the change.