Test Case #:1134 | Test Case Name:Add data validations to Requested Quantity |
System: OpenLMIS | Subsystem: blue |
Test case designed by: Paulina Borowa | Design Date:30.01.2017 |
Short description: As an implementor, I want the requested quantity to override the calculated order quantity so that storeroom managers have the ability manually enter the quantity they approve. If you put this Requested Quantity (J) on your requisition template, then it (J) will be used rather than the calculated Order Quantity field.
|
|
Pre – conditions: |
Step | Action | Expected system response | Comment |
1 | Check if: -data entry validation: If the 'requested quantity' (J) value is different than the "calculated order quantity" (I) then a requested quantity explanation (W) is required | UI side:If (J) value is the same as "calculated order quantity" (I) then a requested quantity explanation (W) is not required:  If: (J) value is different than the "calculated order quantity" (I) then a requested quantity explanation (W) is required API side:If:(J) value is different than the "calculated order quantity" (I) then a requested quantity explanation (W) is required:  (J) value is the same as "calculated order quantity" (I) then a requested quantity explanation (W) is not required:
| |
2 | (J) overrides (I), meaning that any calculations, for example the total RnR cost, should use the quantity entered in J over I when data is entered in both | UI side:API side: |
|
3 | If J is on your template, it is a required field that allows zero or a positive integer (0, 1, 2+) | UI side:it's required allows zero and positive integer
API side: |
|
4 |
| ||
5 | |||
6 |
| ||
7 |
|
