Timeline for TDD - Make the test work quickly, committing whatever sins necessary in process
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15, 2020 at 15:09 | comment | added | candied_orange | @overexchange You’re mixing together two different activities. Code changes come later. | |
| Jun 15, 2020 at 14:56 | comment | added | overexchange | Its a complete de-focus... I mean, let me stabilise by designing my abstractions first. Am being distracted wth these test cases for every code change | |
| Jun 15, 2020 at 14:54 | comment | added | candied_orange | @overexchange by writing the using code first. Sure it won’t compile but it reads just fine. You can call it “on the fly” it you like but it’s a development style that helps you focus on hiding details and showing intent. | |
| Jun 15, 2020 at 14:50 | comment | added | overexchange | Am sorry.....Abstractions doesn't come on the fly... It is a skill to refine the code and create good abstractions. How can you imagine those abstractions and start writing tests? | |
| Jun 15, 2020 at 6:17 | history | edited | candied_orange | CC BY-SA 4.0 |
added 33 characters in body
|
| Jun 15, 2020 at 5:49 | history | edited | candied_orange | CC BY-SA 4.0 |
added 207 characters in body
|
| Jun 15, 2020 at 5:43 | history | answered | candied_orange | CC BY-SA 4.0 |