Creating 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.
About this task
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.
The following topics describe how to create and manage test
cases.- 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. Note that Verify Event steps can only monitor the events that can be displayed in the test client.