Unit testing a Service dotNet rule
Use the unit testing feature to verify that the operations of a Service dotNet rule function correctly before you add the external client 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 on the Integration pages of the Pega Community.
To run a unit test, complete the following steps:
- Save the rule form.
- Start the Tracer by clicking Actions > Trace. For more information, see Tracing services.
- Click Actions > Run.
- Complete the form as described in the following table, and then click Execute.
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:
|SOAP 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 matches the XSD type shown.|
|SOAP Parameter Values||If you selected Specify individual request values for the previous field, enter in the Value field a literal constant value for each Request Parameters row listed on the Request tab. Enter a value that corresponds to the XSD data type shown.|
|SOAP Request Envelope||
If you selected
Supply Soap Envelope
, enter or paste a well-formed and valid XML document in the
SOAP Request Envelope
text area, starting with the <?xml version="1.0"> declaration.
If the service expects requests containing an array element or XML Page elements, a skeleton document is provided as a starting point.
ArticleService dotNet rules