Matt Wynne <[EMAIL PROTECTED]> writes:
> So we've got a pretty decent number of specs now, and despite my best efforts,
> AR is just forcing us down the path of having to use database interaction for
> some of the model specs.
>
> It's starting to get tiring to run all the specs now, which is making me sad,
> and making me worry about how things are going to be in a few months from now.
>
> I'd like to somehow be able to systematically mark the slow example groups as
> being 'impure' and thus be able to choose to mostly ignore them during my
> regular TDD cycle, just running them every so often as a regression.
>
> I'm thinking something like this:
>
> describe "when there are ten users in the database", :slow => true do
>
> What do you think? How are other people solving this problem? Any tips /
> thoughts on how I could implement this?
Why don't you put the specs in a different directory? One layout that
I've seen used (I think by the WePlay guys) is:
spec/
integration/
controllers/
models/
unit/
controllers/
models/
Pat
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
