Run targeted regression testing
When you feed Change Impact into Scenario Generation, AridNova scopes testing to just the services a release touched. Instead of rerunning everything, QA effort lands on the surfaces that actually changed.
Connecting Change Impact to Scenario Generation activates regression testing mode and makes scenario selection release-aware. In the example it targets 47 modified microservices and generates 167 focused regression scenarios — coverage that tracks the release rather than the entire system, so you avoid unnecessary brute-force reruns.

Steps and outcomes
| Action | Expected output | Customer value |
|---|---|---|
| Connect Change Impact to Scenario Generation | The example activates regression testing mode. | Scenario selection becomes release-aware. |
| Target modified microservices | The example targets 47 modified microservices. | QA effort is focused on changed surfaces. |
| Generate focused scenarios | The example generates 167 regression scenarios. | Teams avoid unnecessary brute-force reruns. |