Test Case #:1077
Test Case Name: Associate emergency requisitions with a processing period | |
System: openLMIS | Subsystem: blue |
Test case designed by: Lucyna Laska | Design Date:14.11.2016 |
Short description: API: Acceptance Criteria
UI:
|
|
Pre – conditions: |
Step | Action | Expected system response | Comment |
1 | Find if it's possible to create an emergency requisition for:
Method: GET | Yes, it's possible. It's only one created period that can be included during creating the emergency requisition. | |
2 | Initiate an emergency requisition when user has assigned proper role. | Requisition has been initiated successfully. | |
3 | Initiate an emergency requisition when user does not have assigned proper role. | to update the user roles: URL: http://192.168.1.14/referencedata/api/users?access_token=0a211aa5-2864-4e00-be33-afa8cc70111c Method: PUT Body: { | |
4 | Try to initiate an emergency requisition with wrong period. Method: POST | It's not possible to initiate requisition when suggested period is incorrect. | |
5 | List all emergency requisitions. Method: GET | ||
6 | Try to initiate a few emergency requisition for the same period. Method: POST | The another emergency requisition has been created properly (parameters are still the same as the situation discribed in point 3). | |
7 | Try to delete the emergency requisition. URL: http://192.168.1.14/requisition/api/requisitions/fa2997a7-a652-4772-aafe-e4fd6b1238d9?access_token=adfb41e2-dec6-4905-84cb-bba57e957000 Method: DELETE | The emergency requisition has been successfully deleted. | |
8 | Check if deleted emergency requisition is no longer available. | status 404 not found is returned. Deleted requisition is not available. |
Post – conditions: |