Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Overview

The TestSuite verify the success and failure response of data matching criteria for both services Document Query and Document Retrieve. The TestSuite is run in passthrought, the JMX script is to ensure that the service is in passthrough without the need for server restart.

TestCases Detail for passthrough

The Test cases verify specify matching criteria and assert expected response success or failure.

Document Query TestCases

  • 3.3.1.UT.2 - Find by PatientId (single doc): success

  • 3.3.2.UT.2 - Find by PatientId (multiple docs): success

  • 3.4.1.UT.1 - No matching classcode: success empty response

  • 3.4.1.UT.2 - classcode one: success

  • 3.4.2.UT.2 - matching service starttime: success

  • 3.4.2.UT.2 - matching service stoptime: success

  • 3.4.3.UT.2 - no matching creationtime between: success empty response

  • 3.4.3.UT.2 - creationtime between: success

  • 3.4.3.UT.2 - creationtime left edge: success

  • 3.4.3.UT.2 - creationtime right edge: success

  • 3.4.4.UT.2 - classCode & serviceStartTime: success

  • 3.4.5.UT.2 - creationTime & serviceStartTime: success

  • 3.4.5.UT.2 - creationTime & serviceStopTime: success

  • 3.4.6.UT.2 - creationtime & classCode: success

  • 3.4.7.UT.2 - No Documents Available: success empty response no document match

  • 3.5.2.UT.2 - No Patient Found: success empty response no patient match

  • 3.5.4.UT.2 - Unknown Stored Query: failure response

Document Retrieve TestCases

  • 11.3.1.UT.2 - Single Doc: success

  • 11.3.1.UT.4 - Document Persistence: success

  • 11.3.2.UT.2 - Multiple Doc unique community ID one set: success response with multiple documents

  • 11.4.1.UT.2 - Missing Document: failure response on matching document id

  • No labels