You’ve joined a new team and reviewed the automation code base and have a number of suggestions you want to make to improve the code, or there is a list of outstanding suggestions that need implementing. But where do we start? How can we make such refactors in the least disruptive way?
We can’t just start hacking away at the framework. It’s unlikely we’re going to get weeks/months to make one large refactor and commit, and what happens to all the new tests that need adding during that time? We have to take an incremental approach, targeting the most valuable areas first.
In this workshop we are going to take existing code judgements and improvement suggestions and implement them in a way that maximises our efforts and returns value quickly. You’ll be free to implement these suggestions as you wish, bringing in your own experiences, following our examples, or even vibing with AI if you wish. But the crucial part of this workshop will be demonstrating the changes you’ve made and explaining why you believe they have improved the code. A crucial step in getting buy-in from stakeholders for future improvements or even to have started such work.
*The tests will be written in TypeScript, but the patterns are language agnostic.
