Stuart Roebuck wrote:
> 
> Well I've got got an EmailTransformer I've produced for a current project,
>   it's not too elegant at the moment, but it works, and it has some generic
> unit test code that folk might be interested in for testing the processing
> of a transformer - I don't think there's much unit test code in the
> current Cocoon codebase, infact I think I might be responsible for all of
> it!!.
> 
> If anyone can find the time to relocate it appropriately in the cocoon
> class hierarchy, I have a number of bits of unit testing infrastructure
> that might be handy to other folk:
> 
>         Mock Classes for Avalon:
>                 avalon.excalibur.DataSourceComponent
>         Mock Classes for Framework:
>                 avalon.framework.ComponentManager
>                 avalon.framework.Configuration
>         Mock Classes for Cocoon:
>                 cocoon.environment.Redirector
>                 cocoon.environment.Request
>                 cocoon.environment.Session
>                 cocoon.environment.Source
>                 cocoon.environment.SourceResolver
> 
> These provide sufficient glue to unit test quite a lot of actions,
> generators and transformers in isolation which could also be handy for
> some kinds of performance testing.
> 
> Anyone interested?

I'd be. Make them available somewhere and post the URL.

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<[EMAIL PROTECTED]>                             Friedrich Nietzsche
--------------------------------------------------------------------



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to