Automated Testing
With Automated Unit Testing, you can simplify and increase the speed of unit testing certain aspects of your Process Commander applications. As a result, you can be more agile about determining when corrective action is necessary within your development process.
The benefits of Automated Unit Testing include:
- Early and easy process testing
- Individual and group test management to reduce overhead and speed up the testing process
- Test case retention, because tests are directly associated with the rules themselves
For example, you might have an application with a number of work object types and the flows that process those work objects. Subsequent development work alters one of those flows. Those intended changes made to one flow might have unintended impacts on the application's other work object types and flows. In this situation, the ability to efficiently regression unit test for unexpected results and assess the extent of the impacts is valuable. With Automated Unit Testing, you can quickly discover and address such unanticipated effects.
Using Automated Unit Testing, developers can:
- Create test cases for flows, decision tables, decision trees, activities, and Service SOAP rules
- Run a rule's test case directly from the Test Cases tab of the rule form (Version 6)
- Auto-generate test cases for decision rules
- Run test cases manually, in groups as unit test suites from the Dashboard, or run from the Test Management Framework
- Save results from the test case runs, and use the saved results to compare with past runs and to report on the effects of change
- Instrument flows with flow markers, input fields, and property value differences to allow easier manual unit testing
Additional information
This article links to other Automated Unit Testing resources. Select a version in the table below to display the applicable article.
Topic | Process Commander Version | ||
---|---|---|---|
Overview and configuration | |||
How Automated Unit Testing works | V6.1 | V5.5 | V5.4 |
Enabling Automated Unit Testing | V6.1 | V5.5 | V5.4 |
Creating a testing application and ruleset for test cases and unit test suites | V6.1 | – | – |
Creating a ruleset for test cases and unit test suites | – | V5.5 | V5.4 |
Unit testing – Flow rules | |||
How to test flows with Automated Unit Testing | V6.1 | – | – |
Creating flow rule test cases | – | V5.5 | V5.4 |
Executing flow rule test cases | – | V5.5 | V5.4 |
Create and use a flow marker | V6.1 | V5.5 | V5.4 |
Advanced editing and validation of result pages | V6.1 | V5.5 | V5.4 |
How to define properties to be ignored during flow test case execution | V6.1 | V5.5 | V5.4 |
Unit testing – Decision rules | |||
Create and execute test cases for decision tree and decision table rules | V6.1 | V5.5 | V5.4 |
Auto-generating test cases for a decision table | V6.1 | V5.5 | V5.4 |
Running all test cases for decision tree and decision table rules | V6.1 | V5.5 | V5.4 |
Unit testing – Activity rules | |||
How to unit test activities with the Automated Testing feature | V6.1 | V5.5 | – |
Unit testing – Service SOAP rules | |||
Create and execute test cases for SOAP service rules | V6.1 | V5.5 | V5.4 |
Automated regression testing | |||
Creating a unit test suite from the Test Manager | V6.1 | V5.5 | V5.4 |
Test suite reporting | V6.1 | V5.5 | V5.4 |