Perform manual testing and report POST /register API

[gaurivn]

Description

As a tester,
I need to test POST /register API,
so that I can provide a test report on it.

You should create a markdown file inside /docs/manual_tests with the following content:

• Scenario tested step by step with dummy data you used (e.g.: username and password)
• Report it as:

   * _Test1 Description_  
     _Screenshot/gif_:  
     _Expected Result_:  
     _Actual Result_:
   * _Test2 Description_  
     _Screenshot/gif_:  
     _Expected Result_:  
     _Actual Result_:  
     ... 

If you find a test that the expected result does not match the actual result then create an issue (following Bug Report template), and mention it in your markdown file.

• Make sure to test at least:
  • 1 positive case
  • 1 negative case

Resources:

• Deployed Backend: https://mentorship-backend-temp.herokuapp.com/
• Quality Assurance test cases: /docs/quality-assurance-test-cases.md#register

Acceptance Criteria

Update [Required]

• Test POST /register API
• Create a markdown file under /docs/manual_tests with the content mentioned above (at least 2 tests).

Definition of Done

• All of the required items are completed.
• Approval by 1 mentor.

Estimation

3 hours

[SanketDG]

I am trying to find an intersection between the following issues and the quality assurance table issues opened by @paritoshsinghrahar .

Surely, we are can find a way to sort of find a middle ground here, as I personally do not want repetitive work to be done here.

Let me know your thoughts.

[gaurivn]

I am trying to find an intersection between the following issues and the quality assurance table issues opened by @paritoshsinghrahar .

Surely, we are can find a way to sort of find a middle ground here, as I personally do not want repetitive work to be done here.

Let me know your thoughts.

The issue you mentioned is a first-timers OSH issue - adding a link to the quality assurance tables doc. Whereas this series of issues (manually testing each API) is about documenting them with screenshots for different scenarios.

[SanketDG]

No I mean issues like #758

The point also isn't about the work being different, but whether the work can be put in the same file or not, so that we have a single source of truth.

[gaurivn]

No I mean issues like #758

The point also isn't about the work being different, but whether the work can be put in the same file or not, so that we have a single source of truth.

The issue mentioned would aid this one since it is about updating the test cases. This issue requires the work to be placed in /docs/manual_tests/ as is mentioned here. This series of issues about manually testing each API was brought up during the Mentorship System - Sync up session.

[SHITIZ-AGGARWAL]

I would like to work on this issue , should I comment on it again on 1st sept.

[gaurivn]

Hi @SHITIZ-AGGARWAL, since OSH starts on 1st September 2020, do comment here on Sept 1st and I'll assign you.

[SHITIZ-AGGARWAL]

Hello @gaurivn ,since OSH has begun i would like to work on this issue,
I am new to Open Source so please guide
Really excited to work with the organisation

[ksraj123]

I would like to work on this as a part of opensource hack if no one else is working on it already. Commenting as its 1 sep now so please assign this issue. Thanks

[gaurivn]

Sure assigning you both, @SHITIZ-AGGARWAL, @ksraj123