... hmmm ... anytime we design a method aren't we "storyboarding a GUI"???
Said another way, as we move from worrying exclusively about whether the execution is "correct" to greater code understandability doesn't that distinguish 'unit testing' from 'unit designing'?
toggle quoted message
Show quoted text
--- In testdrivendevelopment@..., Alan Baljeu <alanbaljeu@...> wrote:
So in fact we are talking about designing the user interface of a library (users being other programmers). And concurrently spiking the implementation to get a better idea of what kinds of things you can do. That's more like storyboarding a GUI than coding the guts of an application. Sounds like a fine approach to me.
Only to be clear with words, what you write to drive your API isn't called a test by anyone I've read. It's a driver or a fixture, or a demonstration. Tests are code that decide whether something is correct or not. They pass or fail something. TDD tests are tests in that sense. The "TDD is not about testing" holds because the testing process tries to judge whether an application is correct from a variety of angles while TDD tests aim to create code. It's not testing to Test the code only according to how it was created.
Alan Baljeu
