BDD that shortened regression

Situation

At Zegal, from August 2020 to December 2022, I was the QA engineer on products that included Legal Advice and Clickawill. Regression was taking time the release did not have.

What I built

I automated behavior-driven tests in Java with Selenium and Cucumber. I wrote and maintained the test cases, the test data, and the defect records around them, and I led the testing for those two products, including the conversations where a feature was still being shaped.

How it ran

The suites ran in Jenkins. After a defect was fixed I ran regression again before treating the build as ready. When the same failures kept returning, I took the pattern to the developers so the cause could be removed.

What changed

Regression took less time, and the scenarios gave the team a shared description of what the feature was supposed to do. I also ran sessions with the team on how we were testing and why.

What I would change

I would record how long regression took before the suite and after it. The direction of the change is clear. The number should sit next to it.