When you talk about unit tests are you talking about Unit tests that
are completely stand-alone from a grails application or the
"integration" unit tests that allow you to test with full access to
the Grails environment. (e.g. for domain objects you can do things
like call GORM methods)?
To answer your question in a more general sense, I haven't really
found that much difference in our approach. It was really just getting
used to the mocking framework that Groovy provides and using Expando
objects and understanding the Grails environment itself with regards
to "integration" unit tests. I haven't come across anything that I'd
describe as broken, though I do wish I could write more pure unit test
sometimes, because when you have the kind of test coverage we have,
speed is of the essence. They are slow, especially when you are
running them repeatedly in isolation.
On Thu, Mar 13, 2008 at 6:15 PM, Ray Tayek <
rtayek@...> wrote:
> At 09:18 AM 3/13/2008, you wrote:
> >...
>
> >If we can officially, then we certainly will. Like Jerome said when
> >the dust settles we'd be happy to share some of our experiences. When
> >we met Graeme last month we did talk about doing some kind of case
> >study perhaps. Either way, we'd certainly like to give something back.
>
> one of your team (paul campbell) posted a note about your using an
> agile process. please consider sharing anything you can about unit
> testing domain objects, testing controllers (mock seems to be
> broken), and how the overall testing code structure and organization
> differs from what one would find in a typical java/junit web app
>
> thanks
>
> ---
> vice-chair
http://ocjug.org/>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>
http://xircles.codehaus.org/manage_email>
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email