Re: [macker-developer] Test Driven Development

[Paul C. <can...@po...>]

No, I implemented it using something you might call "function test =20
second" =E2=80=94 I fiddle around, prototyping a feature until I like =
the =20
user experience. I then write a high-level test or set of tests for =20
that feature, which test end results (functional test) and not all =20
the details inside (unit test). In the case of Macker, such a test =20
consists of source code, rules file, and expected output. I then =20
change the code until the test works.

I have used TDD on many projects in the past. It can work well, if =20
the tests are good, although it's not my personal preference. I like =20
prototyping first. I feel like TDD locks me too much into feature =20
checklists (it raises the cost of change early in the cycle), whereas =20=

prototyping first lets me focus on user experience and fluidly rework =20=

features as needed.

Cheers, P


On Sep 23, 2007, at 4:28 AM, Przemys=C5=82aw Szkudlarek wrote:

> Hello
>
> Did you create Macker using Test Driven Development?
>
> Definition from wikipedia.org: "Test-Driven Development (TDD) is a =20
> software development technique that involves repeatedly first =20
> writing a test case and then implementing only the code necessary =20
> to pass the test"
>
> Best regards,
> Przemek
>
> ----------------------------------------------------------------------=20=

> ---
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Macker-developer mailing list
> Mac...@li...
> https://lists.sourceforge.net/lists/listinfo/macker-developer
>
> Macker home page: http://innig.net/macker/
>