Rails - Jan 2008 - Autotest and rspec always tests everything

Is there a way to limit autotest to just what is saved? I have a small
app that as four models/controllers. and testing was fast but testing
everything. I added Restful-Authentication and it tested fine. Now
whenever I save a change to one of my custom controllers, everything
is tested including the authentication and it now takes a long time. I
always thought that AutoTest was only to test things that changed.

I am not sure if it is now just the diff that is taking all the time,
but the number of test it reports each time is very high compared to
the controller I am working on.

Any ideas?

Don French
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

On Jan 2, 2008 8:54 PM, dhf0820-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
<dhf0820-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
>
> Is there a way to limit autotest to just what is saved? I have a small
> app that as four models/controllers. and testing was fast but testing
> everything. I added Restful-Authentication and it tested fine. Now
> whenever I save a change to one of my custom controllers, everything
> is tested including the authentication and it now takes a long time. I
> always thought that AutoTest was only to test things that changed.
>
> I am not sure if it is now just the diff that is taking all the time,
> but the number of test it reports each time is very high compared to
> the controller I am working on.
I believe that this is the way autotest is designed. It only runs a
limited sense when there is a failure, but as soon as that failure is
passing it runs the whole suite. This is the behaviour I would expect
- otherwise I have no way of knowing if changes I make to get one
example passing have any unexpected side effects on other examples.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

So then if something fails, it should just run that test each time
until it passes. Once it passes, everything is run.

Does "Pending" or "not implemented yet" have an impact?  I
have
several "it" statements that are pending. Does that cause it to run
everything or only only when the go between failure and pass

Don French

On Jan 3, 8:15 am, "David Chelimsky"
<dchelim...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> On Jan 2, 2008 8:54 PM, dhf0...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
<dhf0...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
>
>
> > Is there a way to limit autotest to just what is saved? I have a small
> > app that as four models/controllers. and testing was fast but testing
> > everything. I added Restful-Authentication and it tested fine. Now
> > whenever I save a change to one of my custom controllers, everything
> > is tested including the authentication and it now takes a long time. I
> > always thought that AutoTest was only to test things that changed.
>
> > I am not sure if it is now just the diff that is taking all the time,
> > but the number of test it reports each time is very high compared to
> > the controller I am working on.
>
> I believe that this is the way autotest is designed. It only runs a
> limited sense when there is a failure, but as soon as that failure is
> passing it runs the whole suite. This is the behaviour I would expect
> - otherwise I have no way of knowing if changes I make to get one
> example passing have any unexpected side effects on other examples.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

On Jan 3, 2008 5:57 PM, dhf0820-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
<dhf0820-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
>
> So then if something fails, it should just run that test each time
> until it passes. Once it passes, everything is run.
>
> Does "Pending" or "not implemented yet" have an impact?
I have
> several "it" statements that are pending. Does that cause it to
run
> everything or only only when the go between failure and pass
No relation to autotest. The only thing rspec adds to autotest is the
mappings of what spec files go w/ what code. Autotest only cares about
pass/fail. Pending is, as far as autotest is concerned, passing.

HTH.

Cheers,
David
>
> Don French
>
> On Jan 3, 8:15am, "David Chelimsky"
<dchelim...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > On Jan 2, 2008 8:54 PM,
dhf0...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
<dhf0...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >
> >
> >
> > > Is there a way to limit autotest to just what is saved? I have a
small
> > > app that as four models/controllers. and testing was fast but
testing
> > > everything. I added Restful-Authentication and it tested fine.
Now
> > > whenever I save a change to one of my custom controllers,
everything
> > > is tested including the authentication and it now takes a long
time. I
> > > always thought that AutoTest was only to test things that
changed.
> >
> > > I am not sure if it is now just the diff that is taking all the
time,
> > > but the number of test it reports each time is very high compared
to
> > > the controller I am working on.
> >
> > I believe that this is the way autotest is designed. It only runs a
> > limited sense when there is a failure, but as soon as that failure is
> > passing it runs the whole suite. This is the behaviour I would expect
> > - otherwise I have no way of knowing if changes I make to get one
> > example passing have any unexpected side effects on other examples.
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---