A story about why #TestDrivenDevelopment matters
This week, I have been working on an invoicing system in a legacy codebase. The requirements are to extend the invoice report with additional custom fields. What we'll test here is not the visual, but the (in-memory) field values that are ultimately displayed on the invoice report.
So I first wrote the test for the header fields, _let the test fail_, and continued with the actual implementation until the test passed...
1/?
🤖 How can we combine #AI with #TestDrivenDevelopment without losing the human touch? @claresudbery shares insights from her workshop "How Can You Combine AI With Test Driven Development?" and her session "Let’s Stop Making Each Other Feel Stupid" on fostering learning, psychological safety, and human-centered practices in software development.💡
Read the full interview 👉 https://t1p.de/d9p1z
#SAGconf #SoftwareArchitecture #HumanInTheLoop #PsychologicalSafety #TDD #LearningCulture #iSAQB
🤖 How can we combine #AI with #TestDrivenDevelopment without losing the human touch? @claresudbery shares insights from her workshop "How Can You Combine AI With Test Driven Development?" and her session "Let’s Stop Making Each Other Feel Stupid" on fostering learning, psychological safety, and human-centered practices in software development.💡
Read the full interview 👉 https://t1p.de/d9p1z
#SAGconf #SoftwareArchitecture #HumanInTheLoop #PsychologicalSafety #TDD #LearningCulture #iSAQB
Assertion libraries can be considered as mini-DSL’s that make automated tests more readable. When a team of devs make their choice, they usually judge on API preference. While it’s very important to have readable tests, the API should never be the deciding factor. What truly separates a good assertion library is the quality of its failure messages. The more actionable these messages, the faster you’ll diagnose the cause of failing tests.
Assertion libraries can be considered as mini-DSL’s that make automated tests more readable. When a team of devs make their choice, they usually judge on API preference. While it’s very important to have readable tests, the API should never be the deciding factor. What truly separates a good assertion library is the quality of its failure messages. The more actionable these messages, the faster you’ll diagnose the cause of failing tests.
Imagine if only 50% of the energy that is currently used to talk about #LLMs and "#AgenticCoding", was instead used to talk, teach and practice #TDD.
Imagine what kind of #software we will have in either scenario 10 years down the line...
Should Test-Driven Development (TDD) Be Used MORE In Software Engineering? - by the channel Modern Software Engineering:
https://inv.nadeko.net/watch?v=6yb7jKpxTjM
(or YT: https://www.youtube.com/watch?v=6yb7jKpxTjM)
Imagine if only 50% of the energy that is currently used to talk about #LLMs and "#AgenticCoding", was instead used to talk, teach and practice #TDD.
Imagine what kind of #software we will have in either scenario 10 years down the line...
Should Test-Driven Development (TDD) Be Used MORE In Software Engineering? - by the channel Modern Software Engineering:
https://inv.nadeko.net/watch?v=6yb7jKpxTjM
(or YT: https://www.youtube.com/watch?v=6yb7jKpxTjM)
