IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Testing modules > Component testing > Manage test suites > Editing test suites

Create and managing test cases

In addition to enabling you to manage test suites, the test suite editor also enables you to precisely manage the individual test cases that consist of your test suites.

For example, you can create test variations for your test cases and add invocation steps and Wait On steps as required.

Think of a test case as a container for multiple operations that you have selected for testing. Test cases enable you to automate and simultaneously test the operations in the integration test client.

Test cases can have Invoke, Return, Exception, Request, Response, Fine-Grained Trace, and Emulate events. Each event you include becomes a step in the test case. A basic test case automatically includes all Invoke, Return, and Exception events.

You can create a more robust component test case that includes Emulate, Request, Response, and Fine-Grained Trace events. Adding an Emulate event creates an emulator definition step in the test case, and adding a Request, Response, or Fine-Grained Trace event creates a Verify Event step in the test case.

• An emulator definition step allows you to define a series of rules to emulate a component, reference, or human task in a test case. You can use the test data table to specify expected input data and output response data for the components, references, inline human tasks, and stand-alone human tasks that you want to emulate.

• A Verify Event step enables you to verify request, response, or exception data that is passed over a monitor wire between source and target components. It also enables you to verify fine-grained trace data that is returned from a test run. If that Verify Event steps can only monitor the events that can be displayed in the test client.

The following topics describe how to create and manage test cases.

• Adding test cases from the Business Integration view
  

  If necessary, you can create a new test case and add it to an existing test suite. Alternatively, you can create a new test case and simultaneously create a new test suite to contain it.

• Manage test data
  The Test Data Table view enables you to manage your test data in numerous ways.

  For example, you can add variables and choose from a wide selection of variable values.

• Manage test variations
  A test variation is a specific set of variable values for a test case. Although each test case is automatically assigned a default test variation, you can create multiple test variations for a test case that each contain a different set of variable values. When a test case is run, all of the test variations for the test case are run.
• Manage invocations
  In the test suite editor, you can create and manage synchronous and asynchronous invocations, which are used to invoke components and operations.
• Manage Wait On steps
  A Wait On step is used to wait for an asynchronous operation to complete.
• Manage Wait for Time steps
  A Wait for Time step enables a test case to pause for a specified amount of time before continuing execution. This helps synchronize multiple asynchronous calls in a single test case. It also enables you to test more complex scenarios, such as those involving a long-running process that requires multiple interactions.
• Manage Verify Event steps
  A Verify Event step enables you to verify request, response, or exception data that is passed over a monitor wire between source and target components. It also enables you to verify fine-grained trace data that is returned from a test run. If that Verify Event steps can only monitor the events that can be displayed in the test client. There are situations where the SCA run time does not contain enough information for the test client to generate events for some SCA wires. In these cases, a Verify Event steps cannot be used.
• Manage emulator definition steps
  In the test suite editor, you have the choice of adding an emulator that applies to all test cases in a test suite or adding emulator definition steps that apply to specific test cases in a test suite. An emulator definition step allows you to define a series of rules to emulate a component, reference, or human task in a test case. You can use the test data table to specify expected input data and output response data for the components, references, inline human tasks, and stand-alone human tasks that you want to emulate. Also, emulator definition steps enable you to automatically claim and complete your human tasks without using BPC Explorer or Business Space.
• Remove test cases
  

  You can remove any test cases that are listed in the Test Cases area of the test suite editor. This enables you to more easily manage the remaining test cases.

Editing test suites