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] A Campus Spot #86

Closed
arafaysaleem opened this issue Sep 10, 2021 · 0 comments · Fixed by #89
Closed

[DELETE] A Campus Spot #86

arafaysaleem opened this issue Sep 10, 2021 · 0 comments · Fixed by #89
Assignees
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 an admin, I should be able to delete campus spots, so that I can remove old or inconsistent entries.

Acceptance Criteria

GIVEN an admin is deleting a campus spot in the app
WHEN the app hits the /campus-spots/:id endpoint with a valid DELETE request, containing the path parameter:

  • :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: {}

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

{Some complementary notes if necessary}

Testing Notes

Scenario 1: DELETE request is successful:

  1. Create a new campus spot with a POST request to /campus-spots endpoint and ensure status code 200 is returned.
  2. With the id returned from the POST, make a DELETE request to /campus-spots/:id endpoint and ensure status code 200 is returned.
  3. A subsequent GET request to /campus-spots/:id endpoint should return a status code 404.
  4. And the response headers' code parameter should contain "NotFoundException".

Scenario 2: DELETE request is unsuccessful

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

Scenario 3: DELETE request is forbidden:

  1. Make a DELETE request to /campus-spots/:id endpoint using a student account token.
  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 /campus-spots/: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 Sep 10, 2021
@arafaysaleem arafaysaleem changed the title DELETE A Campus Spot [DELETE] A Campus Spot Sep 10, 2021
@arafaysaleem arafaysaleem mentioned this issue Sep 10, 2021
8 tasks
@arafaysaleem arafaysaleem mentioned this issue Sep 13, 2021
15 tasks
@arafaysaleem arafaysaleem linked a pull request Sep 13, 2021 that will close this issue
15 tasks
@arafaysaleem arafaysaleem self-assigned this Sep 30, 2021
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