Regression testing is an important part of working with rules as newly introduced additions or modifications to a rule application may result in unanticipated and undesirable changes to dependent elements.
Consider the following rule application lifecycle:
- A new rule application is authored by an analyst and a minimal set of initial rules are inserted into the rule application.
- Using session testing in irVerify, the analyst establishes that the authored rules satisfy the present date rule requirements.
- The rule application proceeds through the deployment stages of the enterprise, eventually serving as the production record.
- New requirements are issued to the business community from external sources. Working in a staging environment, the analyst authors the new rules in the existing rule application.
- Using session testing in irVerify, the analyst determines that newly introduced requirements are satisfied by the new rules. However, the analyst is unaware that the originally stated requirements are no longer in compliance as a result of the change.
In order for the analyst to guarantee the compliance of a rule modification when new requirements are issued, they must either manually re-test previously validated test data or leverage regression testing with irVerify Test Suites.
It is important the analyst or developer performing tests have a good understanding of the required type of regression testing and how that relates to irVerify. For more information, see the topic on Different Kinds of Regression Tests.
Other topics on irVerify regression testing include the following:
Comments
0 comments
Please sign in to leave a comment.