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

As a product owner, I should be able to create roles, so that I can assign them to persons/laborers #35

Open
arafaysaleem opened this issue Jul 20, 2021 · 0 comments
Labels
user story A brief explanation of a functionality or an interaction with the system, from a user's perspective

Comments

@arafaysaleem
Copy link
Contributor

arafaysaleem commented Jul 20, 2021

Summary

As a product owner, I should be able to create roles, so that I can assign them to persons/laborers.

Acceptance Criteria

GIVEN an product owner is creating a role in the desktop app
WHEN the app hits the /roles endpoint with a valid POST request, containing:

  • role
  • role_type, any one from [app_user,laborer]

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

  • headers
  • role id

Sample Request/Sample Response

headers: {
    error: 0,
    message: "..."
}
body: {
    "role_id": "0",
    "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: POST request is successful

  1. Create a new role with a POST request to /roles endpoint and ensure a 201 status code is returned.
  2. Use the id returned by the response in a subsequent GET request to /roles/:id endpoint and ensure a 200 status code is returned.
  3. Ensure the response contains a role with the correct information i.e. matching the initially sent body.

Scenario: POST request is incorrect

  1. Send a POST request to /roles endpoint with the role_type containing a value not in [app_user,laborer].
  2. Ensure a 422 status code is returned
  3. And the response headers' code parameter should contain an error pointing out failed validation.
@arafaysaleem arafaysaleem added the user story A brief explanation of a functionality or an interaction with the system, from a user's perspective label Jul 20, 2021
@arafaysaleem arafaysaleem mentioned this issue Jul 20, 2021
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
user story A brief explanation of a functionality or an interaction with the system, from a user's perspective
Projects
None yet
Development

No branches or pull requests

1 participant