You are here: Integration > Integration Services category > Service JMS rules > How to unit test a Service JMS rule

How to unit test a Service JMS rule

Use the unit testing feature to verify that the operations of a Service JMS rule function correctly before you add an external component to your testing process.

Unit testing provides only partial evidence of a correct implementation. For more comprehensive information on testing services, see the PDN article Testing Services and Connectors.

Before you begin, see How to provide test data when testing service rules.

To run a unit test, complete the following steps:

  1. Save the rule form.
  2. Optional: Start the Tracer by clicking Actions > Trace. For more information, see Tracing services.
  3. Click Actions > Run.
  4. Complete the form as described in the following table, and then click Execute.

Field

Description
Requestor Context

Select a radio button to define the requestor session is to be used in the test:

  • Use current requestor context — Use your current requestor session (including your RuleSet list, privileges, and current clipboard).

  • Initialize service requestor context — Create a new requestor session based on the APP requestor type and, if the service package requires authentication, another Operator ID instance.
Authentication User ID

If you selected Initialize service requestor context, and the service package instance for the service requires authentication, enter the Operator ID to be used to test the service.
Authentication Password

If you selected Initialize service requestor context, and the service package instance for the service requires authentication, enter a password for the Operator ID.
Enter Request Data

Select a radio button to define the source of request data values for this test:

  • Specify individual request values — This option appears only if all the JMS buffer fields are scalar values, such as strings, numbers, or Booleans.

  • Invoke Initialization activity — A test activity creates values for the JMS request message and for any headers or JMS properties.
Message Header Values

If you selected Specify individual request values for the previous field, enter in the Value field a literal constant value for each header field declared on the Request tab. Enter a value that corresponds to the Java data type listed.
Message Property Values

If you selected Specify individual request values for the previous field, enter in the Value field a literal constant value for each message field declared on the Request tab. Enter a value that corresponds to the Java data type listed.
Message Buffer Values

If you selected Specify individual request values for the previous field, enter in the Value field a literal constant value for each message buffer field declared on the Request tab. Enter a value that corresponds to the Java data type listed.
Activity for Initializing Message Data

If you selected Invoke Initialization activity, enter here the Activity Name key part of an activity that creates JMS message elements. The system assumes the Applies To class of the activity matches the Primary Page Class value on the Service tab. If the activity applies to a different class, enter the class name, a period, and the activity name.

Open topic with navigation