Skip to content

Example from first chapter of 'Refactoring' by Martin Fowler, with tests and translations

License

Notifications You must be signed in to change notification settings

emilybache/Theatrical-Players-Refactoring-Kata

Folders and files

NameName
Last commit message
Last commit date
Jun 8, 2023
Feb 12, 2025
Aug 14, 2024
Mar 22, 2024
Apr 30, 2024
Dec 10, 2024
Apr 12, 2024
Jun 3, 2021
Feb 18, 2025
Feb 17, 2023
Sep 14, 2024
Mar 3, 2024
Aug 25, 2022
Mar 18, 2022
Dec 24, 2022
Mar 18, 2022
Mar 7, 2024
Aug 6, 2019

Repository files navigation

Support this and all my katas via Patreon

Theatrical Players Refactoring Kata

The first chapter of 'Refactoring' by Martin Fowler, 2nd Edition contains a worked example of this exercise, in javascript. That chapter is available to download for free. This repo contains the starting point for this exercise in several languages, with tests, so you can try it out for yourself.

I made a video "Refactoring with Martin Fowler | Theatrical Players Code Kata" that explains a little bit about the exercise and why you should give it a try.

What you need to change

Refactoring is usually driven by a need to make changes. In the book, Fowler adds code to print the statement as HTML in addition to the existing plain text version. He also mentions that the theatrical players want to add new kinds of plays to their repertoire, for example history and pastoral.

Automated tests

In his book Fowler mentions that the first step in refactoring is always the same - to ensure you have a solid set of tests for that section of code. However, Fowler did not include the test code for this example in his book. I have used an Approval testing approach and added some tests. I find Approval testing to be a powerful technique for rapidly getting existing code under test and to support refactoring. You should review these tests and make sure you understand what they cover and what kinds of refactoring mistakes they would expect to find.

Acknowledgements

Thankyou to Martin Fowler for kindly giving permission to use his code.