Did you miss...? BDD isn't really about testing at all. It's about feedback loops and thinking clearly about intent before implementation. The tests are a byproduct — valuable, but secondary to the discipline of thoroughly articulating what you want before you build it.
https://open.substack.com/pub/bosslogic/p/delivering-customer-value-with-bdd
RE: https://mastodon.social/@bosslogic/115984174298880765
“ #TDD and #BDD aren’t really about testing at all. They’re about feedback loops and thinking clearly about intent before implementation.”
Intent first!
Did you miss...? BDD isn't really about testing at all. It's about feedback loops and thinking clearly about intent before implementation. The tests are a byproduct — valuable, but secondary to the discipline of thoroughly articulating what you want before you build it.
https://open.substack.com/pub/bosslogic/p/delivering-customer-value-with-bdd
RE: https://mastodon.social/@bosslogic/115984174298880765
“ #TDD and #BDD aren’t really about testing at all. They’re about feedback loops and thinking clearly about intent before implementation.”
Intent first!
...same for the invoice lines - great, everything's working!✅
I hear you say: "But, Jan, you could have also written the implementation first and then the test - it doesn't really matter, does it!?" - Hold On! We are actually not done yet with our implementation of the requirements! Besides posting and displaying the _real_ invoice, there is often the concept of a so-called "proforma" invoice, which essentially is a "draft" invoice, which is not actually posted and has no invoice number.
2/?
What's to highlight here is that the data sources from which to retrieve the data for the proforma variant are actually _different_ from the ones used for the real invoice. So we need to test and implement this as well!
While we're setting up the test for the proforma invoice (remember: we are doing #TDD!), I'd like to remind you of the first sentence in this thread: we are dealing with a _legacy_ system here: setting up the test is often way more work than doing the actual implementation!
3/?
#introduction I am new here. My brother @jaforbes tells me it is customary to do an opening post of things I find interesting or likely to discuss in the future. Here is my list: #democracy #ai #eng #engineering #osint #geopol #math #mathematics #humanrights #compsci #history #philosophy #space #australia #japan #bluemountains #science #tech #anu #unsw #uts #physics #uai #agi #nafo #peace #ukraine #taiwan #photography #tdd #andor. I have friends everywhere. I hope that you'll join me.
#introduction I am new here. My brother @jaforbes tells me it is customary to do an opening post of things I find interesting or likely to discuss in the future. Here is my list: #democracy #ai #eng #engineering #osint #geopol #math #mathematics #humanrights #compsci #history #philosophy #space #australia #japan #bluemountains #science #tech #anu #unsw #uts #physics #uai #agi #nafo #peace #ukraine #taiwan #photography #tdd #andor. I have friends everywhere. I hope that you'll join me.
#fediHire #fedihelp
I'm still looking for a new #freelance #remote #project in #software #RnD.
I offer #agile ( #team) #coaching or whatever you name it and a lot other stuff. I wouldn't reject any role which I already had, eg. Architect, TeamLead, Product Owner etc...
My skills reach from #Java #Kotlin #Swift #mobile or #backend #TDD #CICD pipelines, project setups or firefighting to #liberatingStructures and merging and splitting teams/departments and organising company wide initiatives.
#fediHire #fedihelp
I'm still looking for a new #freelance #remote #project in #software #RnD.
I offer #agile ( #team) #coaching or whatever you name it and a lot other stuff. I wouldn't reject any role which I already had, eg. Architect, TeamLead, Product Owner etc...
My skills reach from #Java #Kotlin #Swift #mobile or #backend #TDD #CICD pipelines, project setups or firefighting to #liberatingStructures and merging and splitting teams/departments and organising company wide initiatives.
🚀 New chapter added to the Guile Hacker Handbook 🚀
This is a book to learn #Guile in a #TestDrivenLearning style 👽
⬇️ Check it out ⬇️
🇫🇷 🇬🇧 🇮🇹 https://jeko.frama.io
Contrary to what I have said previously, this new chapter is about having some fun using the use-cases in the REPL.
Remember that the “Red” (failing test) part of #TDD is the perfect time to make sure the failure message is useful, instead of the less than helpful “expected actual to not be null”.
🚀 New chapter added to the Guile Hacker Handbook 🚀
This is a book to learn #Guile in a #TestDrivenLearning style 👽
⬇️ Check it out ⬇️
🇫🇷 🇬🇧 🇮🇹 https://jeko.frama.io
Contrary to what I have said previously, this new chapter is about having some fun using the use-cases in the REPL.
Remember that the “Red” (failing test) part of #TDD is the perfect time to make sure the failure message is useful, instead of the less than helpful “expected actual to not be null”.
I now have a GUI for my #rust #GameOfLife
Will optimize the code a bit and try to test _some_ of the UI code with unit tests.
Then I might record a video, since I did not yet find one on youtube where someone implements it in Rust using #TDD (if you know such a video, please forward it to me).
Switched from cargo test to nextest and its output is much nicer. It's also a few seconds faster on a 2-3 minute set of integration tests.
Switched from cargo test to nextest and its output is much nicer. It's also a few seconds faster on a 2-3 minute set of integration tests.
Time for an #introduction I suppose.
I am a full stack developer, former game developer.
I had a lot of exposure to #clojure and #emacs in the last 12 months, and got hooked.
I have been using #tdd for about 15 years.
I like to use #godot for hobby game projects.
#TDD with SwiftUI livestream.
🗓️ Returning Sunday, October 19, Sundays, 9am Pacific, 16:00 UTC
(Cancelled this week, but returning the following Sunday.)
Join longtime iOS unit testing instructor, Jon Reid ( @qcoding), author of "iOS Unit Testing by Example".
https://www.twitch.tv/qcoding
#TDD with SwiftUI livestream.
🗓️ Returning Sunday, October 19, Sundays, 9am Pacific, 16:00 UTC
(Cancelled this week, but returning the following Sunday.)
Join longtime iOS unit testing instructor, Jon Reid ( @qcoding), author of "iOS Unit Testing by Example".
https://www.twitch.tv/qcoding