Testing Services

As an administrator, you can test a service before you publish it. By testing a service, you can submit and run the service before the service is published. When you test a service, a workflow instance is created, and run as if the service were published.

You provide input values and set run properties for the service submission. Test services to ensure that all inputs are formatted properly, the help text and organization of the service is adequate, logic works as intended, and the service runs successfully.

To test the service, select "Run test" from the overflow menu . If there is an approval banner on the service, you can also click Test service in the banner. Then, provide input values and run properties, and submit the service as if it were published. You must run a test service immediately when submitted. You cannot set a run window for a test service.

The approvals for the runAsUser steps must be complete before you can test the service. For more information about the runAsUser steps, see the Details tab of Creating services.

If publishing approval settings are turned on, you do not need approval to publish before you test the service. For more information, see the publishing approval settings in Global settings.

A test service submission runs like any other service submission in Activity and History, but includes [Test] in the Service name in the Activity and History tables. To find your test service submission, include [Test] in your search. You cannot duplicate a test service in History.

Unlike other service submissions, test services are only visible to you and any other administrators.

A test service submission is recorded in History with the [Test] label, even if the service is later published.