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

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.

The following topics describe how to manage emulator definition steps.

• Adding and running emulator definition steps for components
  An emulator definition step for a component enables you to emulate a component or import for a specific test case and use the test data table to specify the expected input data and output response data.
• Adding and running emulator definition steps for references
  An emulator definition step for a reference enables you to emulate a component reference for a specific test case and use the test data table to specify the expected input data and output response data.
• Adding and running emulator definition steps for inline human tasks
  An emulator definition step for an inline human task enables you to emulate an inline human task for a specific test case and use the test data table to specify the expected input data and output response data. It also enables to you to claim and complete the human task automatically.
• Adding and running emulator definition steps for stand-alone human tasks
  An emulator definition step for a stand-alone human task enables you to emulate a stand-alone human task for a specific test case and use the test data table to specify the expected input data and output response data. It also enables to you to claim and complete the human task automatically.
• Editing emulator definition steps for components and references
  In the test suite editor, you can edit an emulator definition step for a component or reference and customize it for specific tests.

  For example, you can select a different interface and operation for the step.

• Editing emulator definition steps for human tasks
  In the test suite editor, you can edit an emulator definition step for an inline or stand-alone human task and customize it for specific tests.

  For example, you can select a different interface and operation for the task.

• Running test suites with unmatched emulator definition steps
  

  If a test suite contains two or more emulator definition steps for the same component, reference or human task and none of the emulator definition steps match, the test run will fail.

• Remove emulator definition steps
  

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

Create and managing test cases