Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

AuditLogging-Standard project is used to test CONNECT's audit logging functionality for PD, DQ, DR, DS, AD, PDDeferred and DSDeferred services in Standard mode. This project got g0, g1 suites with one test case for each service. When this project is executed, there is a script for each test case which validates number of audit entries logged in auditrepo.auditrepository table. The script will also fetch and validate the blob message to make sure it is complying as per Sequoia project checklist and Exchange spec. When auditing turned off using an on the script, it is verified that there are no entries in auditrepo.auditrepository table.

This project works only in loop back setup. 

...

This test case is used to test DS Deferred Request service auditing functionality. When this test case is executed, an on the script will first clear auditrepo.auditrepository table and then submit Document Submission Deferred Request to targeted endpoint. When request sent out and response comes in, auditing will happen and audit entries will be logged into auditrepo.auditrepository table. The script will verify and validate audit entries, audit blob message to make sure audit message are ATNA compliance.  There is an in script that sets LogToDatabase property to false and verifies auditing is not happening. 

...

This test case is used to test DS Deferred Response service auditing functionality. When this test case is executed, an on the script will first clear auditrepo.auditrepository table and then submit Document Submission Deferred Response to targeted endpoint. When request sent out and response comes in, auditing will happen and audit entries will be logged into auditrepo.auditrepository table. The script will verify and validate audit entries, audit blob message to make sure audit message are ATNA compliance. There is an in The script that sets LogToDatabase property to false and verifies auditing is not happening. 

...

This test case is used to test Document Submission service auditing functionality. When this test case is executed, an on the script will first clear auditrepo.auditrepository table and then submit Document Submission Request to targeted endpoint. When request sent out and response comes in, auditing will happen and audit entries will be logged into auditrepo.auditrepository table. The script will verify and validate audit entries, audit blob message to make sure audit message are ATNA compliance. There is an in script that sets LogToDatabase property to false and verifies auditing is not happening. 

...

This test case is used to test PD Deferred Request service auditing functionality. When this test case is executed, an on the script will first clear auditrepo.auditrepository table and then submit Patient Discovery Deferred Request to targeted endpoint. When request sent out and response comes in, auditing will happen and audit entries will be logged into auditrepo.auditrepository table. The script will verify and validate audit entries, audit blob message to make sure audit message are ATNA compliance. There is an in script that sets LogToDatabase property to false and verifies auditing is not happening. 

...

This test case is used to test PD Deferred Response service auditing functionality. When this test case is executed, an on the script will first clear auditrepo.auditrepository table and then submit Patient Discovery Deferred Response to targeted endpoint. When request sent out and response comes in, auditing will happen and audit entries will be logged into auditrepo.auditrepository table. The script will verify and validate audit entries, audit blob message to make sure audit message are ATNA compliance. There is an in script that sets LogToDatabase property to false and verifies auditing is not happening. 

...

This test case is used to test PD service auditing functionality. When this test case is executed, an on the script will first clear auditrepo.auditrepository table and then submit Patient Discovery request to targeted endpoint. When request sent out and response comes in, auditing will happen and audit entries will be logged into auditrepo.auditrepository table. The script will verify and validate audit entries, audit blob message to make sure audit message are ATNA compliance.  There is an in script that sets LogToDatabase property to false and verifies auditing is not happening. 

...

This test case is used to test DQ service auditing functionality. When this test case is executed, an on the script will first clear auditrepo.auditrepository table and then submit Document Query request to targeted endpoint. When request sent out and response comes in, auditing will happen and audit entries will be logged into auditrepo.auditrepository table. The script will verify and validate audit entries, audit blob message to make sure audit message are ATNA compliance.  There is an in script that sets LogToDatabase property to false and verifies auditing is not happening. 

...

This test case is used to test DR service auditing functionality. When this test case is executed, an on the script will first clear auditrepo.auditrepository table and then submit Document Retrieve request to targeted endpoint. When request sent out and response comes in, auditing will happen and audit entries will be logged into auditrepo.auditrepository table. The script will verify and validate audit entries, audit blob message to make sure audit message are ATNA compliance. There is an in script that sets LogToDatabase property to false and verifies auditing is not happening. 

...

This test case is used to test AD service auditing functionality. When this test case is executed, an on the script will first clear auditrepo.auditrepository table and then submit Admin Distribution request to targeted endpoint. When request sent out and response comes in, auditing will happen and audit entries will be logged into auditrepo.auditrepository table. The script will verify audit entries.  NOTE: Audit refactoring for AD service is out of scope for CONNECT-4.6 release, and it functions as per CONNECT-4.5 audit approach. 

...