On Thursday, 20 June 2013 at 09:02:49 UTC, Chris Cain wrote:
On Thursday, 20 June 2013 at 07:36:41 UTC, Paulo Pinto wrote:
...
Just left enough context to ask the following question, I hope
I did not left out too much.
How does TDD then help how a user of my application will use
the application UI?
This is the area where I usually make TDD evangelists go
speechless in conferences, as they start to present ad-hoc
solutions and end up changing subject.
--
Paulo
Sure. The user, in this case, isn't the user of your
application. The "user" is the person using your API (other
programmers). TDD has nothing to do with the visual design of
your application and everything to do with the software
engineering design. It's to help guide you to the answer to the
questions "how should I define the behavior of this class/how
should this class be used in practice?"
UI is also code, composed by functions/classes/markup, depending
on the
language and framework.
How to use TDD to write a class for an owner drawn control in
Win32 as an example?
This is the issue that TDD fails, but TDD advocates keep on
selling it.
--
Paulo
