News for hackers. Stuff that matters.
Re:Verification-First Development by RossBencina on Tuesday March 18, 2025 @05:10PM (#43405169)
> I'd like to redefine TDD [...] don't go through the torment of trying to figure out how to test something that I've not yet even fully designed.

What? The whole point of TDD is that you design the thing by writing the tests. That's why it's called Test Driven.

Re:Verification-First Development by simonw on Tuesday March 18, 2025 @05:48PM (#43405573)
Then it's TDD that I have a problem with.

My main challenge is that I don't know what to call the tests I write, or the process that I use. Calling them "tests" can be confused with manual testing. I usually call them "automated tests" but it's a mouthful and not a term I hear from other people.

Re:Verification-First Development by Jtsummers on Tuesday March 18, 2025 @05:53PM (#43405611)
You call the tests you write tests. I'm not even sure how this is a question. Manual tests and automated tests are terms used in industry, but mostly to distinguish manual versus automated end-to-end or integration tests. And then the only time you'd use the terms is when you have both and feel a need to distinguish them. Otherwise, just call them tests.
Re:Verification-First Development by simonw on Tuesday March 18, 2025 @06:02PM (#43405697)
Yeah, maybe I'm over-thinking this. If I establish that on my projects "make sure to include tests" means automated tests I'll probably be OK.