Automated coverage as the thing that sets the pace
Built automated testing frameworks on Jenkins and Test Studio that cut release cycles by 50% while holding the quality bar, having first taken the organisation from ad hoc testing to over 55% automated coverage.
Quality Engineering, 2016-2019, Ploytech
Testing sat at the end of the process, so it worked as a gate rather than as a feedback loop. The manual regression pass was the single thing setting how often the business could ship, and every release it got a little longer.
The usual response to that pressure is to test less, which trades a visible delay for an invisible risk. That was not an acceptable answer.
Started with coverage, because you cannot shorten a cycle you cannot trust. Built a C# testing framework from scratch, wrote regression suites in Telerik Test Studio, and used JMeter for load and performance, taking automated coverage past 55%.
Introduced Jenkins for continuous integration and automated deployment so that coverage actually ran on every change rather than on request. Automation nobody triggers is just unmaintained code.
Alongside the tooling, introduced Agile practice properly: Jira, Confluence and Service Desk, real backlog management, sprint planning, sizing, standups, reviews and retrospectives. The process change and the automation change only work together.
Release cycles halved, with the quality bar held rather than traded away.
Regression moved from a scheduled event to something that happens continuously, which took the ceiling off how often we could ship.
Test Automation, Jenkins, Telerik Test Studio, JMeter, C#, Agile