You can specify the stubbing settings that depend on the
Message Exchange Pattern defined for the Camel transport.
-
Double-click the operation in the Logical View tab of
Architecture School perspective.
The Operation dialog is displayed.
-
Click the Stub tab.
The Stub tab is
displayed.
-
Complete the following steps in the Stub tab:
-
Click Browse in the Binding panel and select Camel as the required transport in the Select a Resource dialog
box.
Note: The name of the transport is the name you provided to the physical resource of
the Camel component.
-
Select from the following options for the action you
want:
| Option |
Action |
| No |
If you select No, you can select any
transport in the project. |
| Yes |
If you select Yes, you can select only
transports that are referenced (directly or indirectly) by the operation
that contains the test. |
| Only Direct |
If you select Only Direct, you can
select only transports that are referenced directly by the operation that
contains the test. |
-
Click OK.
-
Select Text as the message type
from the list in the Message Type field.
Note: For messages that are not in the Text format, you must
select the Binary option.
-
Add parameters or headers for the messages that you subscribe that depends on the
specifications for the Camel component.
Note: The Default Timeout
section contains common settings for stub replies. No change is required. The
response time is managed by the stubs execution engine in IBM® DevOps Test Integrations and APIs (Test Integrations and APIs).
-
Click OK.
You have configured the stubbing settings in the
operation.
You can now create stubs based on the stubbing settings for
the operation from the Test Factory view.