The code represents a game of Trivial Pursuit, a well known game. If interested you can find the rules here but for the purpose of the refactor kata they aren't really necessary. The goal of the kata is to refactor the code, so the game still works. If you encounter bgs you are allowed to fix them. But make sure the game is correct. It is a refactor not a rewrite.
This code base is a fork from the Legacy Code trivia kata. The repository here has been modified from the original to have the latest versions. So it is less suited for a legacy code retreat and more intended as a pure refactor kata.
Additionally, there is a branch Approval test has added ApprovalTests with optional TCR scripts. Using the kata with these Approval test in place is ideal for practicing pure refactors.
Can you refactor the code without the tests ever breaking? Can you use the TCR scripts?
Not all code options have their versions updated to a more recent version. Not all have added approval tests in the approval test branch. The code options ones that are updated are:
- Java
- Kotlin
- Typescript
- C#
- NodeJS
- PHP
The approval test have scripts added for tcr. Simply run
./tcr
will run the tests, including the approval tests. If the test pass then a commit is done with the default message "WIP" and push to the remote. If the test fail, the changes made are deleted.
This code base is a fork from CaraDojo and J. B. Rainsberger Legacy Code retreat trivia. The repository here has been modified from the original to have the latest versions. So it is less suited for a legacy code retreat and more intended as a pure refactor kata.