997: Associate non-emergency requisitions with the proper period

Test Case #: 997	Test Case Name: Associate non-emergency requisitions with the proper period
System: OpenLMIS	Subsystem: blue
Test case designed by: Anna Czyrko	Design Date:10.11.2016
Short description: Verify that: Regular requisitions are created for the oldest processing-period for which a requisition has not already been created (Note that the “/logistics/periods” endpoint in OpenLMIS v2.0 is defined within RequisitionController.java, and determines which period are displayed on the Requisitions -> Create/Authorize page.) It is possible to filter periods by facility, program, type and date (only periods after given date) we can only use the oldest period which is not associated with any requisition period should be validated. When an earlier requisition was not processed, requisition for next periods cannot be created period for the requisition must belong to a schedule that belongs to the program selected for that requisition

Pre – conditions:

Step	Action	Expected system response	Comment
1	Create RequisitionGroupProgramSchedule with appropriate program, facility and schedule.
2	Create a Requisition with some Period belonging to Scheduled created earlier RequisitionGroupProgramSchedule, program and facility (also with RequisitionGroupProgramSchedule)		It should pass.
3	You make the Requisition with Period, whose schedule is different than createdRequisitionGroupProgramSchedule		Expected result: fail
4
5

Related content