Unit testing a Service MQ rule
Use the unit testing feature to verify that the operations of a Service MQ 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 Pega Community 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:
- Save the rule form.
- Start the Tracer by clicking . For more information, see Tracing services.
- Click .
- 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:
|
| 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:
|
| 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 row 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 Data row listed on the Request tab. Enter a value that corresponds to the Java data type listed. |
| Activity | If you selected Invoke Initialization activity , enter here the Activity Name key part of an activity that creates the information from a test MQ request message. 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. |
Previous topic Unit testing a Service dotNet rule Next topic Unit testing a Service SAP Rule