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 delete a rate type, so that I can remove old or inconsistent rate types #53

Open
arafaysaleem opened this issue Jul 24, 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 24, 2021

Summary

As a product owner, I should be able to delete a rate type, so that I can remove old or inconsistent rate types.

Acceptance Criteria

GIVEN a product owner is deleting a rate type in the desktop app
WHEN the app hits the rate-types/:id endpoint with a valid DELETE request, containing the path parameter:

  • :id, the unique id of the rate type 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 rate type with a POST request to /rate-types endpoint.
  2. With the id returned from the POST, make a DELETE request to /rate-types/:id endpoint.
  3. A subsequent GET request to /rate-types/:id endpoint should return a 404 not found status code.

Scenario 2: DELETE request is forbidden:

  1. Make a DELETE request to /rate-types/:id endpoint using a contractor account token.
  2. Ensure the endpoint returns a 403 forbidden status code.
@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 24, 2021
@arafaysaleem arafaysaleem mentioned this issue Jul 24, 2021
9 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