[Grok-dev] Re: Suggested contents for a skeleton functional doctest

Tres Seaver tseaver at palladion.com
Tue Aug 14 15:45:13 EDT 2007

Hash: SHA1

Martijn Faassen wrote:
> Luciano Ramalho wrote:
>> A fresh grokproject generated sample app passes the doctest below the ###.
>> The doctest shows basic operation of the test browser, and also how to
>> instantiate and exercise the app.
>> I think including a test like this in grokproject will make it much
>> easier for beginning grok users to get in the habit of writing
>> functional tests.
> This is far too much cruft for me. The risk is high that this will be in 
> people's projects forever, broken, distracting. Let's create a document 
> that spells out what to do instead, first.

It is a truism in TDD that "the first test is the hardest."  I can see
real value in generating the first one for a grok project, even if it
does not test "real" application behavior:  perhaps it merely tests that
the application object implements an interface, or something.

Grok is notably test-hostile, at the moment, perhaps becuase of the "low
barrier to entry" mantra.  Testing code *is* tedious to write, but
without it, grok-based projects are going to turn into nighbmares as
they evolve beyond toy stage.

- --
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


More information about the Grok-dev mailing list