As described in Test Unit editor, the Test Unit view provides a graphical view of the interface and provides mechanisms to manipulate the components in the interface.
The Server Context Overlay displays information about the components in the interface within the Test Unit view and enables context menu options for deploying components and manipulating their states.
To enable or refresh the Server Context Overlay as described in the following sections, Integrated Test Environment must be connected to the server. For more information, see the Connect to Server task in Table 29.
When the Server Context Overlay is enabled, icons are added to the icons for each component shown in the Test Unit view to indicate the state of the component. This is useful because all the components that participate in an interface must be running in order to test it.
Figure 70 shows a Test Unit view where the Server Context Overlay is enabled. Most of the components have green arrow icons, indicating they are in a started state. The ClarifyConnector component has an orange circle indicating that it is in a paused state. The collaboration object CustomerSync_ClarifyToCaesar has a red square icon, indicating that it is in a stopped state. Table 31 describes the different component state icons and their meanings.
For information on component states, see the WebSphere InterChange Server: System Administration Guide.
Icon | Meaning |
---|---|
Green arrow | The component is started. |
Orange circle | The component is paused. |
Red square | The component is stopped. |
Question mark | The component is in an unknown state. |
Red circle with white "X" | The component does not exist in the repository. |
Blue checkmark | The component deployed successfully. |
Red "X" | Integrated Test Environment is disconnected from the server, so the Server Context Overlay cannot display the current state of the component. |
To enable the Server Context Overlay, right-click the background of the Test Unit view and select Server Context Overlay from the context menu.
When the Server Context Overlay is enabled, the component state icons appear in the Test Unit view and right-click menu items for the components are enabled.
To disable the Server Context Overlay, right-click the background of the Test Unit view and select Server Context Overlay from the context menu.
To have the Server Context Overlay always appear, enable the Show Server Context Overlay always option in the Integrated Test Environment preferences. Figure 62 shows the Integrated Test Environment preferences.
The state information in the Server Context Overlay is not dynamic, so if the state of a component changes after the Server Context Overlay is initially enabled due to actions external to Integrated Test Environment, then the state information the Server Context Overlay presents will be inaccurate. For instance, if you change the state of a component using the InterChange Server Express Component Management view in System Manager, the Server Context Overlay will still reflect the state of the component prior to the change. Refresh the Server Context Overlay to update it with current state information.
To refresh the Server Context Overlay, right-click the background of the Test Unit view and select Refresh Server Context Overlay from the context menu.
All of the components required for an interface must be deployed to the server repository to test the interface. The Outline view provides a way to work with the InterChange Server Express repository to ensure that it contains the required components.
To deploy a component when it already exists in the server repository, right-click the component in the Test Unit view and choose Deploy with overwrite from the context menu.
To deploy a component if it does not already exist in the server repository, right-click the component in the Test Unit view and choose Deploy from the context menu. If the selected components already exist in the server repository and you use the Deploy option then the deployment will fail.
To remove a component from the server repository using the Test Unit view, right-click the component in the view and choose Remove from server from the context menu.
Entries are written to the Integrated Test Environment Console and InterChange Server Express Console indicating whether the deployment was successful or not.
You can change the state of a component using the Test Unit view. This allows you to resolve problems you discover during testing--you can deactivate the component, modify it, re-deploy it, and re-activate it without using System Manager, repos_copy, or System Monitor.
To change the state of a component, right-click its icon in the Server Context Overlay and choose the desired state operation--Start, Pause, or Stop. Not all component types have all state operations available.
For information on component states, see the WebSphere InterChange Server: System Administration Guide.
You use Client Simulator views to emulate connectors and access clients when testing an interface. Client Simulator views provide interfaces to create business object instances with test data, send them as business object requests, and reply to them as business object responses.
To load the profile for a connector into a particular Client Simulator view, right-click the icon for the connector in the Test Unit view and select Use Client Simulator x, where x is the number of the Client Simulator view position you want to use for that connector.
Table 33 shows the default interface positions in which the different Client Simulator views are displayed.
Views in Integrated Test Environment can be concealed by other views during different stages of a test; for example, a Client Simulator view might be concealed by a BO Inspector view. To reveal a Client Simulator view that is concealed, right-click the connector icon and select Show Client Simulator to give focus to the Client Simulator view.
To close a Client Simulator view, right-click the connector icon and select Close Client Simulator.
For more information on working with Client Simulator views, see Using the Client Simulator view.
If you use business object tracing, Integrated Test Environment records business object data at certain points during the execution of the interface.
To show the business object data for a BO Marker into a particular BO Inspector view, right-click the BO Marker and select Show in BO Viewerx, where x is the number of the BO Inspector view position you want to use for that marker. BO Marker icons are identified in Figure 70.
Table 35 shows the default interface positions in which the different BO Inspector views are displayed.
For more information on using business object tracing, see Table 29.
For more information on working with BO Inspector views, see Using the BO Inspector view.
If you are using business object tracing but have disabled auto-update of the trace information, refresh the BO Markers to update them.
To update BO Markers, right-click the Server Context Overlay and select Refresh BO Markers from the context menu.
If you use business object tracing you can launch Map Designer Express in debug mode for maps that transform generic objects to application-specific objects, using the data produced during the execution of the test within Integrated Test Environment.
Do the following to debug maps using the Test Unit view:
Map Designer Express launches in debug mode with the specified map opened and the specified test data supplied. For more information on how use the debugging features of Map Designer Express, see the WebSphere InterChange Server: Map Development Guide.
There are several options available for changing the scale of the Test Unit view.
To change the Test Unit view scale, right-click the Server Context Overlay and select the desired scale from the context menu. Table 32 lists and describes the scale options.
Test Unit view scale type | Description |
---|---|
Fit Window | This scale deforms the interface illustration to fit the Test Unit view horizontally. |
Fill Window | This scale deforms the interface illustration to fill the Test Unit view. Typically this results in the interface icons being stretched vertically. |
View Normal Scale | This is the default scale. |
View Double Scale | This scale increases the magnification of the interface illustration by two hundred percent. |
Do the following to configure your preferences for the Test Unit view:
Figure 62 shows the Integrated Test Environment preferences.