in reply to Architecting a testing framework for an API
I am trying to come up with a way to build a framework that will let developers code and unit test their yet-to-be-written modules to extend the web application without having to use the actual API code (except for integration testing) and without apache/mod_perl.
That sounds like you want mocks/fakes/stubs here. Take a look at some of the Test Double patterns.
I'm having a hard time trying to figure out is at a high level, how to structure this test framework in such a way that there's not a bunch of code duplication.
Can you give examples of the kind of duplication that you're getting? What's stopping you factoring it out?
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^2: Architecting a testing framework for an API
by mp (Deacon) on Mar 23, 2006 at 22:27 UTC | |
by adrianh (Chancellor) on Mar 24, 2006 at 09:31 UTC |
In Section
Seekers of Perl Wisdom