Failure Logging Testing

Owned by Tran Tang (Unlicensed)
Last updated: Jul 25, 2019
2 min read

Version History:

Version#
Date
Modified By
Description of Modification
1.010/31/2018Paul TambelliniInitial Version

Overview

The following steps are for testing CONNECT Failure Logging functionality.Failure Logging is a tool to view and search/filter failure logging events from the System Administration Module without logging into database to track events. This is a feature that is being introduced in CONNECT release 5.2.

Test Environment Setup:

  1. Deploy CONNECT ear (mvn clean install -P AD,PD,DQ,DR,DS,X12,admingui) and AdminGUI war
  2. Successfully execute ConnectValidation suite before running AdminGUI-Failure Logging test cases
  3. Browse to http://localhost:8080/CONNECTAdminGUI/

Failure Logging:

Expand the Logging menu in the left navigation panel, select Failure Logging, and execute the following tests:

Test ScenarioTest StepsExpected Results
Failure Logging left navigation menu availability
  1. Click on "Logging" from left navigation panel. Click on "Failure Logging" under "Logging".

"Failure Logging" menu item should appear under "Logging".

Clearing failure from Database and creating new failures.


Clear out the eventdb.event

  • Delete from eventdb.event where name = "MESSAGE_PROCESSING_FAILED"

Breaking the ValidationSuite (DocumentRetrieve)

  • Edit internalExchangeInfo_g1.xml in Validation Suite directory by placing a character at RandomChar the end of the URL. 
  • Then run Validation Suite for g1 and populate the failure logging event
Records with the name of "MESSAGE_PROCESSING_FAILED" will be present in the eventdb.event table.
Failure Logging search without providing search parameters in "Search Wizard" under the Failure Logging Tab.
  1. Leave all fields blank under "Search Wizard" and click the "Search" button.

If records are present in eventdb.event table, then list of all the rows will be displayed under, for example,  # event record found table with below information:

(Date, Service, Version, Exception)

  1. Under "event record found" each row will have a radio button when selected "View" button will be  enabled.

Failure Logging Search by providing one or more values in "Search Wizard" under Failure Logging Tab.

  1. Select the service from "Service " dropdown list.

  2. Select exception from "Exception" dropdown list.
  3. Click / and select start time from "Start Time" text field
  4. Click / and select start time from "End Time" text field
  5. Click on Search button.
  6. To tally found  results, check the eventdb.event  table using the credentials that were entered above; Query return results should match to the results displayed on the screen.

If records are present in eventdb.event table, then list of all the rows will be displayed under "event records found" table with below information:

(Date, Service, Version, Exception)

  1. Under "event record found" each row will have a radio button when selected "View" button will be  enabled.

If no rows found, under the Filter Logs tab, the user will see a 0 event records found message.

View  Description Message
  1. Click the radio button from the event record found table which will enable the View button. Click View button.
  2. To close the dialogue window, click X on right top corner of dialogue window.
  1. User will see a child dialogue window with description details. The dialogue window shows a formatted event record.
  2. After closing the dialogue window, the user will be back at the parent window's "event record found" tab and can view other  description data.

user attempts to select limited rows to display for a page
  1. In event records found page, from pagination dropdown select 30 rows to display for a page.

User will see 30 rows display for a page.