From 4fe959325eab8c7842ad182db074744e930b42f6 Mon Sep 17 00:00:00 2001 From: Christian Hujer Date: Sat, 14 Aug 2021 16:25:57 +0530 Subject: [PATCH] Add process. --- README.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 4ff82f92..08744566 100644 --- a/README.md +++ b/README.md @@ -1,14 +1,15 @@ # ExpenseReport -The ExpenseReport legacy code refactoring example in various languages. +The ExpenseReport legacy code refactoring kata in various languages. This is an example of a piece of legacy code with lots of code smells. The goal is to support the following new feature as best as you can: * Add Lunch with an expense limit of 2000. ## Process -1. Read the code to understand what it does and how it works. -2. Read the code and check for design smells. -3. Analyze what you would have to change to implement the new requirement without refactoring the code. -4. Write a characterization test. -5. Refactor the code. -6. Test-drive the new feature. +1. ๐Ÿ“š Read the code to understand what it does and how it works. +2. ๐Ÿฆจ Read the code and check for design smells. +3. ๐Ÿง‘โ€๐Ÿ”ฌ Analyze what you would have to change to implement the new requirement without refactoring the code. +4. ๐Ÿงช Write a characterization test. Take note of all design smells that you missed that made your life writing a test miserable. +5. ๐Ÿ”ง Refactor the code. +6. ๐Ÿ”ง Refactor the test. +7. ๐Ÿ‘ผ Test-drive the new feature.