The Test Suite verifies the success and failure response of data matching criteria for both services Document Query and Document Retrieve. The Test Suite is run in passthrough, the JMX script is to ensure that the service is in passthrough without the need for server restart.
The test cases verify specific matching criteria and assert expected response success or failure.
3.3.1.UT.2 - Find by PatientId (single doc): matching patient id and return single document with success response
3.3.2.UT.2 - Find by PatientId (multiple docs): matching patient id and return multiple documents with success response
3.4.1.UT.1 - No matching classcode: fail to match classcode and return success empty response
3.4.1.UT.2 - classcode one: a single classcode match with multiple documents in a successful response
3.4.2.UT.2 - no matching servicestarttime: fail to match document with service starttime from and to, return successful empty response
3.4.2.UT.2 - matching service starttime: successful match with document on service starttime from and to, return document with successful response
3.4.2.UT.2 - matching service stoptime: successful match with document on service stoptime from and to, return documents with successful response
3.4.3.UT.2 - no matching creationtime between: fail to match document with creation time from and to, return successful empty response
3.4.3.UT.2 - creationtime between: successful match with document creation time from and to, return document with successful response
3.4.3.UT.2 - creationtime left edge: successful match with document creation time from and to, return document with successful response
3.4.3.UT.2 - creationtime right edge: successful match with document creation time from and to, return document with successful response
3.4.4.UT.2 - classCode & serviceStartTime: successful match with class code and service start time from and to, return document with successful response
3.4.5.UT.2 - creationTime & serviceStartTime: successful match with creation time from and to, and service start time from and to, return document with successful response
3.4.5.UT.2 - creationTime & serviceStopTime: successful match with creation time from and to, and service stop time from and to, return document with successful response
3.4.6.UT.2 - creationtime & classCode: successful match with creation time from and to, and class code, return documents with successful response
3.4.7.UT.2 - No Documents Available: no document found patient Id and status type, return successful empty response
3.5.2.UT.2 - No Patient Found: no patient found for patient id, return successful empty response
3.5.4.UT.2 - Unknown Stored Query: fail to match store query id and return failure unknown stored query response
11.3.1.UT.2 - Single Doc: retrieve document with local Home Community ID (HCID), repository and document unique id with single document successful response.
11.3.1.UT.4 - Document Persistence: retrieve document with local HCID, repository and document unique id with document successful response
11.3.2.UT.2 - Multiple Doc unique community ID one set: retrieving multiple document unique ids and expecting multiple documents in successful response
11.4.1.UT.2 - Missing Document: failure to match the document to document unique ids and return failure response