Audit Search
Version History:
Version# | Date | Modified By | Description of Modification |
---|---|---|---|
1.0 | 3/1/2016 | Sailaja Adusumilli | Initial Version |
1.1 | 4/11/2019 | Eric McDonald | Text corrections |
Overview
The following steps are for testing CONNECT Audit Search functionality.Audit Search is a tool to view and search/filter audit logging events from the System Administration Module without logging into database to track events.Â
Test Environment Setup:
- Deploy CONNECT ear (mvn clean install -P PD,DQ,DR,DS,AD,X12,DDS,DDQ,jboss7,was,weblogic,DB,admingui) and AdminGUI war
- Successfully execute ConnectValidation suite before running AdminGUI-Audit Search test cases
- Browse to http://localhost:8080/CONNECTAdminGUI/
Audit Search:
Expand the Logging menu in the left navigation panel, select Audit search, and execute the following tests:
Test Scenario | Test Steps | Expected Results |
---|---|---|
Audit Search left navigation menu availability |
| Audit Search and Failure Logging menu items should appear under Logging. |
Audit search without providing search parameters in "Search Wizard" under the Audit Search Tab. |
| If audit records are present in auditrepo.auditrepository table, then list of all the rows will be displayed under "Audit Records Found" table with below information: (Date, Service, Org Name, Requester, Direction, MessageID, RelatesTo, Audit XML)
|
Audit Search by providing one or more values in Search Wizard under Audit Search Tab. |
| If audit records are present in auditrepo.auditrepository table, then list of all the rows will be displayed under "Audit Records Found" table with below information: (Date, Service, Org Name, Requester, Direction, MessageID, RelatesTo, Audit XML)
If no audit rows found, under the "Patient Search" tab, the user will see a "Audit Records not Found" message. |
Audit Search by providing messageId & RelatesTo in Search Wizard under Audit Search Tab. |
| If audit records are present in auditrepo.auditrepository table, then list of all the rows will be displayed under "Audit Records Found" table with below information: (Date, Service, Org Name, Requester, Direction, MessageID, RelatesTo, Audit XML)
If no audit rows found, under the "Patient Search" tab, the user will see a "Audit Records not Found" message. |
Audit Search by providing "Start time, End time, Requester/user, service, Organization" and "relatesTo, MessageId" in "Search Wizard" under search Tab |
| If audit records are present in auditrepo.auditrepository table, then list of all the rows will be displayed under "Audit Records Found" table with below information: (Date, Service, Org Name, Requester, Direction, MessageID, RelatesTo, Audit XML)
If no audit rows found, under the "Audit Search" tab, the user will see a "Audit Records not Found" message. |
View Audit Blob Message |
|
|
User attempts to search by providing Start time and End time |
| User will see an alert message showing " The EndTime should be greater than startTime". |
Validation of messageId, RelatesTo and Requester/User |
| User will see an alert message showing below Messages: "Enter valid MessageId" "Enter valid Requester/User" |
user attempts to select limited rows to display for a page |
| User will see 30 rows display for a page. |
NOTE:
- As of (3/2/2016) AuditSearch tab covers only happy path testing. There are tickets opened in back log to address negative test cases and front end validations. (FHAC-885 , FHAC-744, FHAC-758, FHAC-861). This wiki will be updated after addressing negative testcases / validations functionality for AuditSearch tab.Â
- Audit Search on messageId will look for all audit records that start with "urn:uuid:" . As per specifications messageID format will be "urn:uuid:xxxxxxxx:xxxx:xx"