As a contractor, I should be able to get details of a single label, so that I can understand what kind of work it describes/represents.
Acceptance Criteria
GIVEN a contractor is requesting details of a label in the desktop app
WHEN the app hits the labels/:id endpoint with a valid GET request, containing the path parameter:
:id, the unique id of the label for which the details are needed.
THEN the app should receive a status 200AND in the response, the following information should be returned:
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
This endpoint is accessible by and serves the product owner in the same way.
Testing Notes
GIVEN a contractor is requesting details of a label in the desktop app
WHEN the app hits the labels/:id endpoint with a valid GET request, containing the path parameter:
:id
THEN the app should receive a status 200AND the {id} in the body should be same as the :id in the path parameter
Summary
As a
contractor
, I should be able to get details of a single label, so that I can understand what kind of work it describes/represents.Acceptance Criteria
GIVEN a
contractor
is requesting details of a label in the desktop app WHEN the app hits thelabels/:id
endpoint with a valid GET request, containing the path parameter::id
, the unique id of the label for which the details are needed.THEN the app should receive a status
200
AND in the response, the following information should be returned:Sample Request/Sample Response
Resources
Dev Notes
This endpoint is accessible by and serves the product owner in the same way.
Testing Notes
GIVEN a
contractor
is requesting details of a label in the desktop app WHEN the app hits thelabels/:id
endpoint with a valid GET request, containing the path parameter::id
THEN the app should receive a status
200
AND the{id}
in the body should be same as the:id
in the path parameter