How to unit test a Service Email rule |
C-2431Use the unit testing feature to verify that the operations of a Service Email 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 Testing Services and Connectors, a document in the Integration area of the Pega Developer Network.
Before you begin, see How to provide test data when testing service rules.
To run a unit test, complete the following steps:
CTRL
+ R
.
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 | |
Message Header Values |
Enter one value for each message header declared on the Request tab. |
Message Content |
Optional. Type or paste in the text that forms the content of the arriving email message. |
Activity for adding attachments |
Optional. If the arriving test message is to include email attachments, identify here the Activity Name key part of the test activity described above. |