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 Post #140

Closed
Tracked by #18
arafaysaleem opened this issue Oct 16, 2021 · 0 comments · Fixed by #145
Closed
Tracked by #18

[POST] A New Post #140

arafaysaleem opened this issue Oct 16, 2021 · 0 comments · Fixed by #145
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 a student, I should be able to create posts, so that I can get reactions on them.

Acceptance Criteria

GIVEN an student is creating a post in the app
WHEN the app hits the /posts endpoint with a valid POST request, containing:

  • body text
  • privacy enum('public','private','limited')
  • author_erp varchar(5),
  • posted_at datetime
  • resources array, where each item contains:
    • resource_url varchar(150)
    • resource_type enum('image','video')

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

  • headers
  • post id

Sample Request/Sample Response

headers: {
    error: 0,
    message: "..."
}
body: {
    "post_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 post entry with a POST request to /posts endpoint with author_erp == erp in student account token and ensure a 201 status code is returned.
  2. Use the id returned by the response in a subsequent GET request to /posts/:id endpoint and ensure a 200 status code is returned.
  3. Ensure the response contains a post with the correct information i.e. matching the initially sent body.
  4. Clean up the database by sending a DELETE request to /posts/:id endpoint and ensure a 200 status code is returned.

Scenario 2: POST request is incorrect

  1. Send a POST request to /posts 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 /posts endpoint with author_erp != erp in student account token.
  2. Ensure the response returns a 403 forbidden status code.
  3. And the response headers' code parameter should contain "ForbiddenException"

Scenario 4: POST request is unauthorized

  1. Send a POST request to /posts 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 16, 2021
@arafaysaleem arafaysaleem mentioned this issue Oct 16, 2021
13 tasks
@arafaysaleem arafaysaleem self-assigned this Oct 19, 2021
@arafaysaleem arafaysaleem mentioned this issue Oct 20, 2021
27 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