Regression Test
Regression testing is the process of re-running previously executed tests on our platform. This is to ensure that recent changes such as new features, bug fixes, or updates have not introduced new defects or broke existing behaviours. It helps maintain stability and ensures that updates do not negatively affect the user experience.
Why is it Important?
- Detects unintended issues: Confirms that changes do not break existing behaviours.
- Maintains quality: Ensures decision services and workflows continue to work as expected after updates.
- Supports continuous improvement: Enables teams to deliver updates confidently and reliably.
When to Perform Regression Testing
Regression testing should be performed whenever there are:
- New decision, workflow or test suites additions
- Modifications to existing decision, workflow or test suites
- Changes to configuration or integration points
- New releases, bug fixes or patches by the platform product
How It Works
- Execute Tests: Run all the available test cases within the project
- Compare Results: Check that the outcomes match expected results and that no new defects are introduced.
Note: Any additions or modifications to workflow or decision should include (additional) test cases or test suites to cover areas that could be affected.
The navigation starts at row 3 because rows 1 and 2 in the Excel sheet are reserved for titles. In the example below, there is only one row of test data, so it appears as row 3.
Things To Note
If any errors occur, rows with errors are displayed first, making it easier for users to identify and address them quickly.
Next Steps
Once all regression tests pass successfully:
Publish Changes - After validating your decision or workflow through regression testing, publish your changes to save them. This will unlock any draft decision or workflow, and their status will be updated as Published. With that, all published decision, workflow, test suites are available for release management.
