Setting preferences for the integration test client
By default, the user-definable preferences for the integration
test client are already optimized for testing modules and components.
However, in the course of your testing activities, you may find that you want
to change some preferences.
The following topics provide information on setting preferences for
the integration test client:
Enabling modified resources to be saved automatically
If you attempt to start the test client when there are modified files that have not been saved, the test client will not start and you will be prompted to save the files. However, you can select a preference that enables the modified resources to be saved automatically when you start the test client.
Specifying the default action when a module requires republishing
If automatic publishing is not enabled for your server and the module that you are testing requires republishing, the default action is for the test client to automatically open a dialog box that prompts you to choose whether to automatically republish your module before continuing your current test. However, you can set a preference that enables you to change the default action.
Specifying the default action when a module requires restarting
If automatic publishing is not enabled for your server and the module that you are testing requires restarting, the default action is for the test client to automatically open a dialog box that prompts you to choose whether to automatically restart your module before continuing your current test. However, you can set a preference that enables you to change the default action.
Specifying the default action when publishing to a server
If you are running one or more tests in the test client and you manually publish a module to the server, the default action is for a dialog box to open that prompts you to choose whether to stop your publishing or stop your tests and continue your publishing. However, you can set a preference that enables you to change the default action.
Selecting business graph properties to display in the integration test client
In WebSphere Integration Developer, a business graph is a wrapper that is added around a simple business object or a hierarchy of business objects to provide additional capabilities, such as carrying change summary and event summary information related to the business objects in the business graph. If you want to test a component that uses a business graph, you can select specific business graph properties to manage as attributes in the value editor of the integration test client. This enable you to pass or return values for the business graph attributes, which is especially useful if you are working with EIS systems, such as CICS®.
Specifying the maximum depth of expanded business objects
In the integration test client, nested business objects are automatically expanded to a depth of five levels in the value editor and zero levels in the data pool editor. However, you can change the maximum depth to which you want to automatically expand your nested business objects.