[rspec-devel] mock framework

David Chelimsky dchelimsky at gmail.com
Wed Aug 22 15:12:01 EDT 2007


On 8/22/07, aslak hellesoy <aslak.hellesoy at gmail.com> wrote:
> On 8/22/07, Jay Levitt <lists-rspec at shopwatch.org> wrote:
> > aslak hellesoy wrote:
> > > On 8/22/07, Carl Porth <badcarl at gmail.com> wrote:
> > >> +1, but what framework will rspec's generators use?  Should there be
> > >> a translator? and what framework should the translator translate to?
> > >>
> > >
> > > A translator from what to what? The RSpec mock framework will still
> > > exist, it's just being factored out.
> >
> > But then RSpec and its example specs will be using an unmaintained mock
> > framework that we don't recommend anyone else use?
> >
>
> Perhaps, but I don't see a compelling reason to migrate RSpec's own
> specs to use a new mocking framework (yet). We have a framework that
> works quite nicely for our needs.
>
> Unmaintained code doesn't stop working, it just stops to evolve.

One way this could work would be to modify the generators to use a
mock_adapter based on rspec's current mocking framework. Then we'd
have a model that could be followed for the other frameworks.

In the long run, I do want rspec mocks to fade away, not just to
remain un-evolving. But there is no urgency for this.

David

>
> Aslak
>
> > Jay
> >
> > _______________________________________________
> > rspec-devel mailing list
> > rspec-devel at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/rspec-devel
> >
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel
>


More information about the rspec-devel mailing list