Burkhard Carstens wrote:
> I do know about testframeworks. It's just, I am not the kind of
> developer, that defines/writes the tests first then writes the
> functionality ...
I'm of the same opinion, I find the test first church a bit too radical.
So I prefer a more general term like test driven development that
comprises the refactoring of the existing code in an agile development
practice.
> So I'd rather like to define the test when the main functionality is
> there, just to verify every now and then, that my changes/tunings
> didn't break something ..
>
> Guess, I am not the only one with this strategy, that's why I think your
> tool would be a great thing to have integrated in fpc...
You are not the only one for sure. Btw the automation of the creation of
the empty skeletons is usefull anyway, even in the test first practice
one frequently creates a sketch of the class interface to have an idea
of the interaction he would like to have with the class.
Regards,
Dean
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives