Test the Diff, Not the App
The pull request is merged, the regression suite stays green, and then a customer discovers that checkout is broken.
The problem isn't simply when the tests ran. The suite checked behavior the team already knew about, while the PR introduced something new that no existing test covered. Moving the regression run closer to merge doesn’t really catch what the suite has missed.
As code changes faster, this becomes harder to ignore. Dynamic PR testing creates and runs tests for the specific changes in a pull request against a live version of the application before it merges. The diff defines what gets tested, rather than the existing regression suite.
Dynamic PR testing brings application verification into the pull request before the change is merged
Why Teams Keep Growing Their Regression Test Suites
Traditional test automation operates on a reactive loop. A feature is released, after which someone looks at it manually,...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE