The application posts HTTP Post requests to a soap component endpoint. 
   
It dynamically modifies soap messages to trigger various exception cases.

The application is run via a basic CLI.

**Main Menu**

{{:development:applications:ebondingtesting:main_menu.png|}}

  * 0 Run all message and exception checks
  * 1 Send a Create message check response & run all Create exception checks
  * 2 Send a Verify message check response & run all Verify exception checks
  * 3 Send a Modify message check response & run all Modify exception checks
  * 4 Send a Verify  check response & run all Cancel exception checks
  * 5 Send a Retrieve check response & run all Retrieve exception checks
  * 5 Trigger AVC messages and check responses
  * 6 Send messages in order chosen by user, supports Create, Cancel, Verify, Modify & Retrieve messages
  * 7 Basis manual load testing, send the desired number of create & cancel messages

For Create, Verify, Modify, Cancel, & Retrieve options a sub menu allows the user to run all commands related to that message, or run a single exception check command. See menu options below.

**Create Menu** 

{{:development:applications:ebondingtesting:create_menu.png|}}

**Verify Menu**

{{:development:applications:ebondingtesting:verify_menu.png|}}

**Modify Menu**

{{:development:applications:ebondingtesting:modify_menu.png|}}

**Cancel Menu**

{{:development:applications:ebondingtesting:cancel_menu.png|}}

**Retrieve Menu**

{{:development:applications:ebondingtesting:retrieve_menu.png|}}

Application creates a testReport.txt in the root of the application. Please note if you choose option 0 from the main menu or run all create commands the last Check/Exception will be a fail; this is because this checking for a Processing Failure Exception which will only occur when the ticketer is down.

**Test Report**

{{:development:applications:ebondingtesting:test_report.png|}}

If you run into any issues please ensure that the values in the config file are correct. This located at config/EbondingConfig. Please ensure that the following are correct: postUrlEndpoint, ebondingDatabaseUrl, & soapDatabaseUrl. See example below with values set for local testing.

{{:development:applications:ebondingtesting:config_file.png|}}