We’ve all been there. You update a small piece of text or fix a tiny CSS bug. You push the code, and then… you wait. Your CI pipeline decides that this minor tweak means it needs to run your entire end-to-end regression suite.
It’s slow, it’s expensive, and honestly, it’s a sledgehammer to crack a nut.
If you tuned into Selenium Conference this year, you might have caught Simon Stewart’s talk. He hit on a topic that every team struggling with slow deployments needs to hear: we need to stop running things just because they are there.