Question is, would you duplicate the specs for all the classes that include a certain module (through shared behaviour for example), or would you use one set of specs for just the module, and specify that a class should include that module?
On Sun, Feb 24, 2008 at 12:19 AM, Pat Maddox <[EMAIL PROTECTED]> wrote: > On Thu, Feb 21, 2008 at 8:09 AM, Chuck Remes <[EMAIL PROTECTED]> > wrote: > > While practicing BDD on my first-ever BDD project, I have come to a > > point where it makes sense to change my original class to an abstract > > class and create one (or more) concrete subclasses that implement a > > specific method. What is the right way to restructure the tests in > > this scenario? Do I leave the existing tests in place and just create > > a new spec file that instantiates and tests the concrete subclass? > > > > I think I can continue to instantiate my "abstract" parent as long as > > I don't go near the behavior that will be defined by the concrete > > subclasses. Is that the right thing to do? > > > > Thanks for any hints. > > > > cr > > _______________________________________________ > > rspec-users mailing list > > rspec-users@rubyforge.org > > http://rubyforge.org/mailman/listinfo/rspec-users > > > > I think that shared example groups might be useful. > > Pat > _______________________________________________ > rspec-users mailing list > rspec-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >
_______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
