Using the Test Unit view

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.

Using the Server Context Overlay

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 19.

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.

Figure 65 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 21 describes the different component state icons and their meanings.

For information on component states, see the System Administration Guide.

Figure 65. Test Unit view with Server Context Overlay enabled


 
 

Table 21. Component state icons and meanings
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.

Enabling and disabling the Server Context Overlay

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.

Refreshing the Server Context Overlay

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 then the state information will be inaccurate. For instance, if you change the state of a component using System Monitor, the Server Context Overlay will still reflect the state of the component prior to the change. You must 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.

Managing component states using the Test Unit view

You can change the state of a component within Integrated Test Environment. 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 Start Artifact, Pause Artifact, or Stop Artifact.

For information on component states, see the System Administration Guide.

Deploying components using the Test Unit view

To deploy a component using the Test Unit view, right-click the component in the view and choose Deploy Artifact from the context menu.

Entries are written to the ITE Console and ICS Console indicating whether the deployment was successful or not.

Note:
The term "artifact" is a synonym for component which appears in some interfaces.

Using, showing, and closing Connector Agent views

You use Connector Agent views to emulate connectors and access clients when testing an interface. Connector Agent 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 Connector Agent view, right-click the icon for the connector and select Use Test Connectorx, where x is the number of the Connector Agent view position you want to use for that connector.

Table 23 shows the default interface positions in which the different Connector Agent views are displayed.

If the profile for a connector is already loaded in a Connector Agent view, but is concealed by another view (such as a BO Inspector view), you can right-click the icon for the connector and select Show Test Connector to give focus to the Connector Agent view.

If the profile for a connector is already loaded in a Connector Agent view, you can right-click the icon for the connector and select Close Test Connector to close the Connector Agent view.

Note:
This option not only closes the Connector Agent view, but also causes the Connector Agent view to stop emulating the connector.
For more information on working with Connector Agent views, see Using the Connector Agent view.

Showing BO Inspector views

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 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 65.

Table 25 shows the default interface positions in which the different BO Inspector views are displayed.

For more information on using business object tracing, see Table 19.

For more information on working with BO Inspector views, see Using the BO Inspector view.

Refreshing BO Markers

If you are using business object tracing but have disabled auto-update of the trace information then you must explicitly 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.

Debugging maps using the Test Unit view

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:

  1. Enable the Server Context Overlay as described in Enabling and disabling the Server Context Overlay.
  2. Enable business object tracing by using the Task Manager as described in Using the Task Manager view.
  3. When you have sent a business object through the interface, right-click the icon for the map you want to debug and select Debug Map from the context menu.
  4. At the "Select a BO Instance" window select the business object instance you want to use and click OK.

  5. 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 Map Development Guide.

Note:
Map Designer Express executes independently of Integrated Test Environment. Integrated Test Environment does not continue to communicate with Map Designer Express after you launch it.

Changing the Test Unit view scale

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 22 lists and describes the scale options.

Table 22. Test Unit view scales and descriptions
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.

[ Top of Page | Table of Contents ]

Copyright IBM Corp. 1997, 2003