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 Class #181

Closed
arafaysaleem opened this issue Nov 29, 2021 · 0 comments · Fixed by #205
Closed

[DELETE] A Class #181

arafaysaleem opened this issue Nov 29, 2021 · 0 comments · Fixed by #205
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

arafaysaleem commented Nov 29, 2021

Summary

As a student, I should be able to delete classes, so that I can remove old or inconsistent entries.

Acceptance Criteria

GIVEN a student is deleting an class in the app
WHEN the app hits the /classes/:term_id/:class_erp endpoint with a valid DELETE request, containing the path parameter:

  • :class_erp, 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 (Admin):

  1. Create a new class with a POST request to /classes endpoint using an admin account token and ensure a 200 status code is returned.
  2. Make a DELETE request to /classes/:term_id/:class_erp endpoint using an admin account token and ensure a 200 status code is returned.
  3. A subsequent GET request to /classes/:term_id/:class_erp endpoint should return a status code 404.
  4. And the response headers' code parameter should contain "NotFoundException".

Scenario 2: DELETE request is unsuccessful due to unknown class_erp

  1. Make a DELETE request to /classes/:term_id/:class_erp endpoint containing a non-existent class_erp.
  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 /classes/:term_id/:class_erp endpoint for using 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 /classes/:term_id/:class_erp 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 user story A brief explanation of a functionality or an interaction with the system, from a user's perspective Type: Feature labels Nov 29, 2021
@arafaysaleem arafaysaleem self-assigned this Nov 29, 2021
@arafaysaleem arafaysaleem mentioned this issue Nov 29, 2021
9 tasks
@arafaysaleem arafaysaleem mentioned this issue Dec 13, 2021
15 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