https://github.com/rstraub/theatrical-players-kata-scala

Theatrical Players Refactoring Kata Kotlin
https://github.com/rstraub/theatrical-players-kata-scala

Last synced: 3 days ago
JSON representation

Theatrical Players Refactoring Kata Kotlin

• Host: GitHub
• URL: https://github.com/rstraub/theatrical-players-kata-scala
• Owner: rstraub
• Created: 2024-02-21T07:48:06.000Z (12 months ago)
• Default Branch: main
• Last Pushed: 2024-03-30T20:41:02.000Z (10 months ago)
• Last Synced: 2024-12-03T03:15:04.533Z (2 months ago)
• Language: Shell
• Size: 63.5 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Theatrical Players Refactoring Kata

Based on

the [kata by Emily Bache](https://github.com/emilybache/Theatrical-Players-Refactoring-Kata)https://github.com/emilybache/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.

## 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.