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

[POST] A New Reaction Type #130

Closed
arafaysaleem opened this issue Oct 15, 2021 · 0 comments · Fixed by #135
Closed

[POST] A New Reaction Type #130

arafaysaleem opened this issue Oct 15, 2021 · 0 comments · Fixed by #135
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 create reaction types, so that students can select one while interacting with posts.

Acceptance Criteria

GIVEN an admin is creating a reaction types entry in the app
WHEN the app hits the /reaction-types endpoint with a valid POST request, containing:

  • reaction_type

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

  • headers
  • reaction type id

Sample Request/Sample Response

headers: {
    error: 0,
    message: "..."
}
body: {
    "reaction_type_id": "1",
    "affected_rows": 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

{Some complementary notes if necessary}

Testing Notes

Scenario 1: POST request is successful

  1. Create a new reaction type entry with a POST request to /reaction-types endpoint and ensure a 201 status code is returned.
  2. Use the id returned by the response in a subsequent GET request to /reaction-types/:id endpoint and ensure a 200 status code is returned.
  3. Ensure the response contains an reaction type with the correct information i.e. matching the initially sent body.
  4. Clean up the database by sending a DELETE request to /reaction-types/:id endpoint and ensure a 200 status code is returned.

Scenario 2: POST request is incorrect

  1. Send a POST request to /reaction-types endpoint with an incorrect key name in the body
  2. Ensure a 422 status code is returned
  3. And the response headers' code parameter should contain "InvalidPropertiesException".
  4. And the response headers' data parameter should contain the name of the invalid parameter.

Scenario 3: POST request is forbidden

  1. Send a POST request to /reaction-types endpoint with a student account token.
  2. Ensure a 403 forbidden status code is returned.
  3. And the response headers' code parameter should contain "ForbiddenException"

Scenario 4: POST request is unauthorized

  1. Send a POST request to /reaction-types 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: High 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 15, 2021
@arafaysaleem arafaysaleem mentioned this issue Oct 15, 2021
8 tasks
@arafaysaleem arafaysaleem self-assigned this Oct 15, 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