To test an end-to-end flow, the functional testing typically involves accessing different applications integrated for running the flow. In order to execute the integration tests, create flows that span multiple applications. These flows send/receive information to and from different applications.

To perform complete end-end tests, add the URL as an attribute in the properties file as follows:

configuration.properties

# Integration Environments gStrMWMApplication=https\://<server name>\:<port>/ouaf/webservices/ gStrCCBAppliation=https\://<server name>\:<port>/ouaf/webservices/ gStrMDMAppliation=https\://<server name>\:<port>/ouaf/webservices/

Following is the example where the Oracle Utilities Customer Care and Billing service AT-C1Premise is called.

Test data:

 

Note that this test data is a combination of environment and application service names.

In cases where the integration environments used for testing have different authentication credentials (userID/password), support is provided for setting the username and password for each environment. To enable this support, in the configuration.properties file, provide the user name/password variable prefixed with the environment URL variable, separated by an underscore.

Following is an example that extends the above integration environments example to use different user names and passwords for each environment:

configuration.properties

Setting user name/password for a Oracle Utilities Customer Care and Billing service:

 

Setting user name/password for a Oracle Utilities Mobile Workforce Management service:

The sample configuration file in this case is as follows.

configuration.properties

By default, Oracle Utilities Testing Accelerator automatically constructs the web service end point URL based on the web service name provided in the flow test dataand the application URL provided in the flow/user configuration sets. To configure a component in a flow to post a request to a different application as part of an integration flow, the following configuration needs to be added to either the flow configuration set or the user configuration set.

Define the environment configuration properties pertaining to the second Oracle Utilities Enterprise application with which integration testing should be done. Example: Integration testing between Oracle Utilities Customer Care and Billing and Oracle Utilities Meter Data Management.

Prefix them with a custom keyword. This keyword is used in the component's test data in a flow to specify the application configuration context to a component for running it.

Example: Assume that Oracle Utilities Customer Care and Billing is the application to be used with Oracle Utilities Meter Data Management for integration testing where the Oracle Utilities Meter Data Management environment details are set as default against the flow and user configuration sets and the Oracle Utilities Customer Care and Billing application's access details are to be specified. Assume the custom keyword chosen to specify the Oracle Utilities Customer Care and Billing details is “CCB”. In the flow configuration set or user configuration set, use the “Add Property” option, and add the following properties.

CCB property holds the external web service end point URL prefixed up to but not including the web service name. If the web service end point URL for the WSDL of person object in CCB is https:myccbserver.mycompany.com/webservices/ATC1PersonAdd?WSDL, the CCB property should hold the value - “myccbserver.mycompany.com/webservices/”.

The properties CCB_gStrApplicationUserName and CCB_gStrApplicationUserPassword hold the user name and password respectively for authenticating the user posting the web service request to Oracle Utilities Customer Care and Billing.

The integration flow in Oracle Utilities Testing Accelerator may contain a mix of components to two or more Oracle Utilities Enterprise applications. To get a component in flow to post a request to the on-premise Oracle Utilities Enterprise applications, the web service name in the component step's test data should be prefixed with the keyword.

In the example where Oracle Utilities Customer Care and Billing is the application with which integration testing needs to be performed for Oracle Utilities Meter Data Management and “CCB” is the keyword, the web service name for the C1-PersonAdd component's test data in the integration flow should be specified as “CCB/ATC1PersonAdd”. This ensures that the C1- PersonAdd component posts the request to Oracle Utilities Customer Care and Billing whose configuration has been specified in the flow configuration set or user configuration set using the keyword prefix “CCB”.

During the integration flow run, the flow configuration set and user configuration set that have the required environment properties should be selected.

More than one such configuration can be set so that a test flow can interact with multiple applications. Each application can have its own custom keyword which is used while specifying the web service name in the component step's test data in a flow.