Download to read offline
Uploaded byMani Sarkar
Refactoring developer habits
The document discusses the importance of developer habits, particularly in the context of the Test-Driven Development (TDD) life-cycle, emphasizing the need to recognize and refine positive and negative habits. It outlines a structured approach to TDD's red-green-refactor cycle and shares guiding principles for effective testing and refactoring. Additionally, it invites community discussion and emphasizes continuous improvement and collaboration among developers.
More Related Content
Similar to Refactoring developer habits
Refactoring developer habits
- 1.
- 2. @theNeomatrix369 @pedromsantos We arecreatures of habit...
- 3. @theNeomatrix369 @pedromsantos ..our habitsinfluence our actions greatly...
- 4. @theNeomatrix369 @pedromsantos Know andaccept your good habits !
- 5. @theNeomatrix369 @pedromsantos Know andaccept your bad habits !
- 6. @theNeomatrix369 @pedromsantos Developer habitsis a very broad subject
- 7. @theNeomatrix369 @pedromsantos But weneed to start somewhere
- 8. @theNeomatrix369 @pedromsantos The TDDlife-cycle
- 9. @theNeomatrix369 @pedromsantos Let’s fitit into the TDD cycle Red-Green-Refactor cycle
- 10. @theNeomatrix369 @pedromsantos The TDDcycle ⇐ apply habits... Red phase ⇐ apply habits... Green phase ⇐ apply habits... Refactor phase ⇐ apply habits...
- 11. @theNeomatrix369 @pedromsantos Refactoring Developer Habits: birth ofthe #TDD #manifesto
- 12.
- 13.
- 14. @theNeomatrix369 @pedromsantos Refining: afterdiscussion 1
- 15. @theNeomatrix369 @pedromsantos Refining: afterdiscussion 2
- 16.
- 17. @theNeomatrix369 @pedromsantos Just beforeSocrates UK 2016, Pedro and Mani...
- 18. @theNeomatrix369 @pedromsantos Repeat thesame exercise
- 19.
- 20. @theNeomatrix369 @pedromsantos What shouldbe removed?
- 21.
- 22. @theNeomatrix369 @pedromsantos Should theflow be improved?
- 23. @theNeomatrix369 @pedromsantos Give moreor less importance to any item?
- 24.
- 25. @theNeomatrix369 @pedromsantos Results ofthe discussions
- 26. @theNeomatrix369 @pedromsantos Shared withthe community Github: http://bit.ly/1tjLS7l
- 27. @theNeomatrix369 @pedromsantos Principles - testsshould test one thing only - test one logical assertion - don't mix assertions of state and collaboration in the same test - modifications of production code should only break related test cases - each test should be self-contained, including data - ensure tests are independent of each other - don't refactor with a failing test - organise your unit test projects to reflect your production code - keep your tests and production code separate - do not use production data and code to test production code - if your tests are difficult to write or maintain, consider changing the design
- 28. @theNeomatrix369 @pedromsantos Red phase -create more specific tests to drive a more generic solution (Triangulate) - give your tests meaningful names (behaviour / goal-oriented) that reflect your production system - write the assertion first and work backwards - see the test fail for the right reason - ensure you have meaningful feedback from failing tests
- 29. @theNeomatrix369 @pedromsantos Green phase -write the simplest code to pass the test - write any code that makes you get to the refactor phase quicker - it is okay to write any code that you might improve at a later stage
- 30. @theNeomatrix369 @pedromsantos Refactor phase -refactor aggressively and constantly - treat tests as first class code - use the IDE to refactor quickly and safely - refactor production and test code independently (except changing public interfaces)
- 31.
- 32. @theNeomatrix369 @pedromsantos Does TDDlead to good design? Find out... http://codurance.com/2015/05/12/does-tdd-lead-to-good-design/
- 33. @theNeomatrix369 @pedromsantos Discuss withthe community http://SoftwareCraftsmanship.slack.com channel: #tdd
- 34. @theNeomatrix369 @pedromsantos Big “thankyou” to the first contributors http://bit.ly/235Ub3a
- 35.
- 36. @theNeomatrix369 @pedromsantos Thanks to@jasongorman for sharing the original list
- 37.