Skip to content
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

[DELETE] Cancel A Sent Hangout Request #128

Closed
Tracked by #17
arafaysaleem opened this issue Oct 14, 2021 · 0 comments · Fixed by #129
Closed
Tracked by #17

[DELETE] Cancel A Sent Hangout Request #128

arafaysaleem opened this issue Oct 14, 2021 · 0 comments · Fixed by #129
Labels
Status: Completed Type: Feature user story A brief explanation of a functionality or an interaction with the system, from a user's perspective

Comments

@arafaysaleem
Copy link
Collaborator

Summary

As a student, I should be able to cancel a hangout request, so that I can prevent a meetup.

Acceptance Criteria

GIVEN a student is cancelling a hangout request in the app
WHEN the app hits the /hangout-requests/:id endpoint with a valid DELETE request, containing the path parameters:

  • id, the unique id of the entity being removed

THEN the app should receive a status 200
AND in the response, the following information should be returned:

  • header message indicating delete operation success

Sample Request/Sample Response

headers: {
    error: 0,
    message: "The specified item was deleted successfully"
}
body: {
    rows_removed: 1
}

Resources

  • Development URL: {Here goes a URL to the feature on development API}
  • Production URL: {Here goes a URL to the feature on production API}

Dev Notes

None

Testing Notes

Scenario 1: DELETE request is successful (Sender cancels)

  1. Create a new hangout request with a POST request to /hangout-requests endpoint and ensure status code 201 is returned.
  2. Use the id from the response to make a DELETE request to /hangout-requests/:id endpoint using a token with erp == sender_erp.
  3. Ensure status code 200 is returned.
  4. A subsequent GET request to /hangout-requests/:id endpoint should return a status code 404.
  5. And the response headers' code parameter should contain "NotFoundException".

Scenario 2: DELETE request is unsuccessful due to unknown id

  1. Make a DELETE request to /hangout-requests/:id endpoint containing a non-existent hangout_request_id in path parameter.
  2. Ensure a 404 status code is returned.
  3. And the response headers' code parameter should contain "NotFoundException"

Scenario 3: DELETE request is forbidden due to unowned hangout request

  1. Make a DELETE request to /hangout-requests/:id endpoint using a student account token with erp !== sender_erp.
  2. Ensure the endpoint returns a 403 forbidden status code.
  3. And the response headers' code parameter should contain "ForbiddenException"

Scenario 4: DELETE request is unauthorized

  1. Send a DELETE request to /hangout-requests/:id endpoint without an authorization token
  2. Ensure a 401 unauthorized status code is returned.
  3. And the response headers' code parameter should contain "TokenMissingException"
@arafaysaleem arafaysaleem added Priority: Low Status: Pending Type: Feature user story A brief explanation of a functionality or an interaction with the system, from a user's perspective labels Oct 14, 2021
@arafaysaleem arafaysaleem mentioned this issue Oct 14, 2021
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Completed Type: Feature user story A brief explanation of a functionality or an interaction with the system, from a user's perspective
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant