...
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. | Without assigned proper role, user can't initiate requisition. | 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 | All emergency requisitions can be displayed by using the 'emergency' parameter in request. | |
6 | Try to initiate a few emergency requisition requisitions 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. | |
9 | Try to submit the emergency requisition. | ||
10 | Try to authorize the emergency requisition. | ||
11 | try to approve the emergency requisition. | ||
12 | Try to convert to order the emergency requisition. | ||
TESTING PROCESS USING UI. | |||
1 | Log in to main UI. | User should be logged in. | |
2 | Find the emergency requisitions for proper facility and program. | The list with emergency requisition is displayed. | |
3 | Try to submit the emergency requisition. | The emergency requisition has been successfully submitted | |
4 | Try to authorize the emergency requisition. | The emergency requisition has been successfully authorized. | |
5 | Go back to the view with all emergency requisitions for the same facility and program as above. | The list with all emergency requisition is available. | |
6 | Try to initiate a new emergency requsiition. | The new row for initiating the emergency requisition with status: Not yet started is available. User can initiate a new emergency requisition once previous one is authorized (I'm allowed to, since my previous one is waiting for approval). | |
7 | Go back to the view with requisitions ready for approve. | The list with all emergency requisitions is displayed. | |
8 | Reject the emergency requisition. | The emergency requisition has been successfully rejected. | |
9 | Go back to the view with all emergency requisition for the same facility and program as earlier. | Two requisitions with status INITIATED are visible. User can act upon both of them (the one that came back because of being rejected and the new one, that I've initiated, because I was allowed to). |
Post – conditions: |