LIST
https://rbcs-us.com/documents/Why-Most-Unit-Testing-is-Waste.pdf Mention: Article_ TDD is dead. Long live testing. - David Heinemeier Hansson Mention: Video_ Writing Software - David Heinemeier Hansson Mention: Video_ Software Architecture vs. Code - Simon Brown
https://martinfowler.com/articles/is-tdd-dead/ Other notes Article_ TDD is dead. Long live testing. - David Heinemeier Hansson Video_ Is TDD dead_ 1_ TDD and Confidence [[video-is-tdd-dead-1-tdd-and-confidence.md|]]Video_ Is TDD dead_ 2_ Test-induced design damage [[video-is-tdd-dead-2-test-induced-design-damage.md|]]Video_ Is TDD dead_ 3_ Feedback [[video-is-tdd-dead-3-feedback.md|]]Video_ Is TDD Dead_ 4_ Costs of Testing [[video-is-tdd-dead-4-costs-of-testing.md|]]Video_ Is TDD dead_ 5_ Answering Questions
https://dhh.dk/2014/tdd-is-dead-long-live-testing.html http://www.rbcs-us.com/documents/Why-Most-Unit-Testing-is-Waste.pdfPaper_ Why Most Unit Testing is Waste - James O Coplien Video_ Writing Software - David Heinemeier Hansson
Is TDD dead? 1: TDD and Confidence https://www.youtube.com/watch?v=z9quxZsLcfo 3 things that bother me What is a unit test can’t have colaborators can’t touch db, file system fast, <1s -> no use out of unit tests that don’t talk to colaborators Driving arch through mocks mock heavy&enabling arch testing induced damage “Unit testing all the things” Red-Green-Refactor sometimes it works sometimes it does not work === What is a unit test KentBeck output tape, input tape, then build it personality, anxiety test-first appeared later...
Is TDD dead? [Part II] (test-induced damage) https://www.youtube.com/watch?v=JoTB2mcjU7w and it got there one test at a time one design decision at a time TDD puts evolutionary pressure on a design testability puts pressure on a design question of grain-size continuum of granularity of tests cost of every layer of indirection TDD is addicting No, desire for isolation is causing this result. isolation is the driver you cannot isolate yourself from backend/db/in-memory/webservice how much are we willing to spend, to get how much decoupling cohesion vs coupling willing to suffer high coupling, so I can have high...
Is TDD dead? [Part III] (feedback) https://www.youtube.com/watch?v=YNw4baDz6WA === Kent Feedback instant feedback is not always possible how far can we? how frequently feedback? 100ms – minutes fidelity of feedback green + prod -> % no crash different kinds of software different personalities overhead lifespan years & probabilities === Martin there is more than one thing you want feedback on User needs “is this software doing something useful for the user?” “how do I want to visualise the UI”...
Is TDD Dead? 4: Costs of Testing https://www.youtube.com/watch?v=dGtasFJnUxI === David other half of trade-offs things are not free pressures and nudgings over-testing “never write a single line of prod code without writing a test” multiples of lines of test code per prod code what is the right ratio? how many 9’s ? === Kent delta-coverage how much does a test test which none others do if you have multiple tests covering one behaviour, you have coupling...
Is TDD dead? 5: Answering Questions https://www.youtube.com/watch?v=gWD6REVeKW4 === What is an example of an open source project that does TDD well? @David common code open source only extracts commons, libraries only personal experiences of private apps @Martin takes a lot of effort to understand the code bases where these problems occur team of 12 for a year when you’re not working on it @Kent JUnit project @David Are we scientific? virtually impossible to true/false it’s still worth debating...
TDD, Where Did It All Go Wrong - Ian Cooper https://www.youtube.com/watch?v=EZ05e7EMOLM Book_ Refactoring - Martin Fowler Book_ Refactoring to Patterns - Joshua Kerievsky Book_ Test Driven Development_ By Example - Kent Beck Article_ Is TDD Dead_ - Martin Fowler Ian Cooper - TDD, Where Did It All Go Wrong https://www.youtube.com/watch?v=EZ05e7EMOLM Trigger for writing test != new method != new class = requirement test api System Under Test (SUT) !...
Problem: dependency Symptom: duplication Write failing test BEFORE writing any code Remove duplication get to green ASAP, quick&dirty: Pattern_ Fake it until you make it Pattern_ TDD Obvious Implementation tests driving code: Pattern_ Triangulation Results: organic design vs over-engineered code courage vs fear rest between self testing code Split up design getting code to work because they are conflicting activities Model_ The Three Laws of TDD [[pattern-put-a-bad-feeling-into-a-test.md|Pattern_ Make the change easy....