http://qs321.pair.com?node_id=538891


in reply to Re: Architecting a testing framework for an API
in thread Architecting a testing framework for an API

Thank you for the link. The Patterns of xUnit Test Automation site is very helpful in thinking about all of this and is not a site I had seen before.

I don't have a lot of duplication yet, since this project is still in the early stages of development, but I am expecting there to be quite a bit of "test fixture setup" that is repeated from one test to the next (mainly setup of mock objects or subroutine overrides), possibly with variations in the setup data between tests. I think you're right, though, this will be something that can be factored out.

  • Comment on Re^2: Architecting a testing framework for an API

Replies are listed 'Best First'.
Re^3: Architecting a testing framework for an API
by adrianh (Chancellor) on Mar 24, 2006 at 09:31 UTC
    I am expecting there to be quite a bit of "test fixture setup" that is repeated from one test to the next (mainly setup of mock objects or subroutine overrides), possibly with variations in the setup data between tests.

    Ah. Then this is stuff that Test::Class can help with. You can stick all your repeated fixture setup in a (wittily named) :setup method. You can specialise fixtures with subclassing. That said - wait until you get the duplication before you factor it out would be my advice.