Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/lurumad/theatrical-players-refactoring-kata
https://github.com/lurumad/theatrical-players-refactoring-kata
Last synced: 9 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/lurumad/theatrical-players-refactoring-kata
- Owner: lurumad
- License: mit
- Created: 2023-11-07T05:57:31.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2024-09-05T07:58:50.000Z (2 months ago)
- Last Synced: 2024-09-06T12:55:21.922Z (2 months ago)
- Language: C++
- Size: 371 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: license.txt
Awesome Lists containing this project
README
Theatrical Players Refactoring Kata
====================================The first chapter of ['Refactoring' by Martin Fowler, 2nd Edition](https://www.thoughtworks.com/books/refactoring2) 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.
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](https://medium.com/97-things/approval-testing-33946cde4aa8) 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.