From adf56c6bd11469b3ac2f170a34430ed44d3174f0 Mon Sep 17 00:00:00 2001 From: Emily Bache Date: Wed, 7 Aug 2019 09:14:54 +0200 Subject: [PATCH] add link to my recent article --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 63b709f..0616f50 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,7 @@ Refactoring is usually driven by a need to make changes. In the book, Fowler add 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. +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 ----------------