Skip to content

Shield Test

calexh-sar edited this page Feb 4, 2021 · 5 revisions

Overview

The CR Connect Configurator lets you run a "Shield Test" in order to check the validity of any workflow specification. This can be done at two levels:

  1. On the Workflow Specification page (insert graphic link from Mike here)
  2. While configuring the BPMN or DMN file (insert graphic link from Mike here)

Clicking on the shield icon in either level runs a series of tests on the Workflow Specification, i.e., it will attempt to test BPMN, DMN and template files associated with the workflow specification. The shield test engine will randomly populate form fields for all user tasks and run two passes, one with all fields and one with only required fields. Since the fields are randomly populated, for complex workflows it is possible that not all paths are tested each time.

Messages for up to two errors generated while testing the workflow are displayed in a pop-up from the bottom of the page. At the very least the error message shown is pulled directly from the Python interpreter. In many cases the effort has been made to present these error messages first in clear layman's terms, followed by the more technical explanation.

Understanding the Error Message

Specific Errors

Dependent Fields Must be Required

If a field found later in the form or another task is dependent on a value generated in another field, that field must be required.

Hidden and required field must have a default value