About Tdd

by Helio Rui Ramos Freitas

Test Driven Development (TDD) (WIP)

Basics of TDD.

What is the advantage of writing tests first? One must trully understand what he or she is implementing in order to implement it well. Writing tests firsts helps the developer to think about the design of the code may look like before it is written. It gives direction when following the RED, GREEN, REFACTOR cycle, and once the tests are complete, it is like a small specification of how the code should behave was created. TDD gives confidence when making changes, and help newcomers to understand the expected behaviour of the code.

Does it always help?

Should I write it first or write ir last?

Why?

Different styles of TDD.

• Outside in (London style)

What style to use when?

references:

https://martinfowler.com/bliki/TestDrivenDevelopment.html

https://www.youtube.com/watch?v=llaUBH5oayw

https://bitfieldconsulting.com/golang/test-last-development

https://hackernoon.com/test-driven-development-is-fundamentally-wrong-hor3z4d

https://charleeli.medium.com/why-tdd-is-bad-and-how-to-improve-your-process-d4b867274255

https://medium.com/@learnstuff.io/difficulties-in-using-tdd-41429cf1e6e3#:~:text=The%20main%20problem%20with%20Test,functional%20only%20on%20happy%20flows.

https://stackoverflow.com/questions/3204241/how-can-you-implement-test-driven-development-with-legacy-code

https://philippe.bourgau.net/initiate-your-team-to-tdd-for-legacy-code-with-the-gilded-rose-kata/

https://nvoulgaris.com/comparing-tdd-flavours/