Gateway Properties Editor Testing

Owned by Tran Tang
Last updated: Jul 25, 2019
Version#DateModified ByDescription of Modification
0.12/24/2015Sailaja AdusumilliInitial Version

Overview:

The following steps are for testing CONNECT gateway configuration functionality.

Test Environment Setup:

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

Properties

Expand the Properties menu in the left navigation panel, select Gateway, and execute the following tests:

Test ScenarioTest StepsExpected Results
Navigate to Gateway Properties configuration tab
  1. Select Properties -> Gateway from the left navigation panel

User will be able to see Gateway Properties tab with a list of available properties.

The Gateway tab shows list of property rows with below fields:

1.Key : keys from the gateway.properties file
2.Description: Property description, defined as comments in the gateway.properties file
3.Value: property value.


Edit Property Value
  1. In the UDDIMaxResults row, click on the Value in the far right column. Change the value to 505.
  2. Check gateway.properties and verify that the value is 505
  3. In the UDDIMaxResults row, click on the Value in the far right column. Change the value to 500
  4. Check gateway.properties and verify that the value is 500

When a value is changed, an info box will appear describing the change that has just been made. In this case, you will see the following two messages:

  • INFOProperty value changed for UDDIMaxResults from 500 to 505.
  • INFOProperty value changed for UDDIResults from 505 to 500.
Edit Property Setting - Negative case
  1. From "Gateway Properties" tab right click on value related any X12 document submission key
  2. Update / comment property value with "#".

User will be able to comment the selected x12 document submission key successfully.

User will see an info alert as property changed.

From the SOAPUI-validation suite enable "RealTimeTransaction TestCase" and run the test. The result will be fail.


(Note: This property will be picked up only if the server is re-started. After updating for testing purpose/reverting back (restoring) it will require re-start.)