Testing Overview
Build smarter, test safer, and deploy faster—all without leaving the visual interface.
Testing in Decisions refers to the suite of tools such as Unit Tests, Debugger, Step Simulation, Rule validation, and Front-end/UI testing that lets you validate flows, rules, and user interfaces before deploying them. Testing is important because it helps catch logic errors, ensures data is handled correctly, reveals broken workflows, and minimizes production risk.
The Unit Test Results Page is a dashboard within any Designer Project that aggregates all Unit Tests for flows/rules in that project (and optionally sub-folders). Key features include:
Running all unit tests for the current folder or including sub-folders.
Running tests per flow or single tests.
Editing, copying, or deleting unit tests directly from the dashboard.
Yes, Decisions supports robust integrations with third-party testing tools such as Apache Jmeter.
Front-end / UI testing in Decisions is about automating user interactions in portals, forms, or UI components to ensure that the user-facing parts behave correctly. Key elements:
Using tools like Selenium combined with NUnit for browser automation, simulating user actions (data entry, form navigation).
Using the Decisions.UnitTests.Web DLL (or similar helper libraries) to locate form controls/components via unique identifiers (e.g., data-component-id) to interact or assert on UI.