Comment on page

What is a Scenario in Process Testing?

Understand how Scenarios work within Process Testing.


What is Process Testing?

Use Process Testing to evaluate runtime behavior of a Process. Process Testing provides the following benefits:
  • Automate testing: Eliminate manual, repetitive testing that allows Process Designers to evaluate specific behaviors and workflow. Automate multiple runs against a series of test data. Tasks in each test automatically simulate completion. Validation requirements within Screens for Form Task and Manual Task elements are ignored.
  • Reduce time to delivery: Greatly accelerate the time to design and deliver sophisticated, complex Processes to production.
  • Increase the quality of solution delivery: More rapidly evaluate, identify, and debug specific behaviors in the business solution.
  • Test without starting Requests: Instead, Process Testing mocks Requests using mock Request data. Therefore, Process Testing does not trigger log events nor affect Save Search results.
  • Specify the scope of the Process Test: Testing can run either end-to-end or from a midway breakpoint. The breakpoint may be the Process model object from which to begin your evaluation: automate the test run to that object, and then manually test the remainder of that mock Request. Tests do not need to be started from the starting object in the Process. A test may be started from a selected object when preparing to run a test.

What is a Process Scenario?

A Process Scenario contains the scope of a Process Test run using mock Request data. Create Scenarios from that Process's configuration, and then run them from the Process model in Process Modeler.
Process Testing can automate multiple runs against a series of test data in the Scenario. Tasks in each test automatically simulate completion using the mock Request data.
Last modified 23d ago