Forum: RSpec autospec is not picking latest changes

Hey Guys.

I just updated a project form 1.1.4 that was working with autotest
3.10 without issues:

1) Updated spec/model/project_spec.rb and it fired only that spec.
2) Updated app/model/project.rb and it fired only the matching spec 
file.

After the update of rspec and rspec-rails as plugins a few minutes
ago, it only run the controller specs and no other. Also, it doesn't
matter which file I change, always run the same set of controller +
model files.

Running old "autotest" only, it happens the same.

Since the loading and matching mechanism changed a few revisions back,
I'll like to know if someone else is facing similar situation (or I'm
just the one with the awkward environment).

Thanks in advance,
--
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

On Tue, Sep 16, 2008 at 4:18 PM, Luis Lavena <luislavena@gmail.com> 
wrote:
> matter which file I change, always run the same set of controller +
> model files.
>

Forgot to include environment information:

Rails 2.1.1
ZenTest 3.10.0

rspec, 3b3a59313097efceb9f9e4e400e1e87f6531f304
rspec-rails, 5bb22b4d6b01f3b88c0e54730157855572eb40aa

Ruby 1.8.6, patchlevel 114 (i386-mingw32)

Also tested with i386-mswin32, with same results.

--
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

try script/autospec instead - I always use that these days. not sure
what the difference is.
On 16 Sep 2008, at 20:20, Luis Lavena wrote:

>>
>
> -
> Human beings, who are almost unique in having the ability to learn  
> from
> the experience of others, are also remarkable for their apparent
> disinclination to do so.
> Douglas Adams
> _______________________________________________
> rspec-users mailing list
> rspec-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

cheers,
Matt
----
http://blog.mattwynne.net
http://songkick.com

In case you wondered: The opinions expressed in this email are my own
and do not necessarily reflect the views of any former, current or
future employers of mine.

On Tue, Sep 16, 2008 at 4:41 PM, Matt Wynne <matt@mattwynne.net> wrote:
> try script/autospec instead - I always use that these days. not sure what
> the difference is.

Thank you for your feedback Matt,

Tried both, the same result.

The funny thing is that another Rails 2.1.1 application works without
problems under the same scenario with both autotest and
script/autospec.

--
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

On Tue, Sep 16, 2008 at 12:45 PM, Luis Lavena <luislavena@gmail.com> 
wrote:

>
> The funny thing is that another Rails 2.1.1 application works without
> problems under the same scenario with both autotest and
> script/autospec.
>

That sounds like a plugin difference, then.

///ark

On Tue, Sep 16, 2008 at 5:22 PM, Mark Wilden <mark@mwilden.com> wrote:
> On Tue, Sep 16, 2008 at 12:45 PM, Luis Lavena <luislavena@gmail.com> wrote:
>>
>> The funny thing is that another Rails 2.1.1 application works without
>> problems under the same scenario with both autotest and
>> script/autospec.
>
> That sounds like a plugin difference, then.
>

Only two plugins installed: rspec and rspec-rails :-D

--
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

On Tue, Sep 16, 2008 at 1:45 PM, Luis Lavena <luislavena@gmail.com> 
wrote:

>
> Only two plugins installed: rspec and rspec-rails :-D
>

Sure - I was just suggesting you check that they were the same versions 
in
both projects. That would be one way the projects could behave 
differently
with autotest.

///ark

On Tue, Sep 16, 2008 at 6:05 PM, Mark Wilden <mark@mwilden.com> wrote:
> On Tue, Sep 16, 2008 at 1:45 PM, Luis Lavena <luislavena@gmail.com> wrote:
>>
>> Only two plugins installed: rspec and rspec-rails :-D
>
> Sure - I was just suggesting you check that they were the same versions in
> both projects. That would be one way the projects could behave differently
> with autotest.
>

Same version (using git and manually copied over).

Also after the update my color output started act weird, but that
another issue that I must investigate.

--
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

On my side I updated the rspec gem and rspec_rails plugins and now 
autotest and autospec are not working anymore.  autospec does nothing at 
all and autotest starts but does not execute the specs

I'm on windows vista.

Rémi

Matt Wynne wrote:
> try script/autospec instead - I always use that these days. not sure
> what the difference is.
> On 16 Sep 2008, at 20:20, Luis Lavena wrote:
> 
>>>
>>
>> -
>> Human beings, who are almost unique in having the ability to learn  
>> from
>> the experience of others, are also remarkable for their apparent
>> disinclination to do so.
>> Douglas Adams
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users@rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
> 
> cheers,
> Matt
> ----
> http://blog.mattwynne.net
> http://songkick.com
> 
> In case you wondered: The opinions expressed in this email are my own
> and do not necessarily reflect the views of any former, current or
> future employers of mine.

Hi,

I am facing a similar problem. Actually what happens, is that when I 
edit specs and then save, then autospec detects it and runs the specs, 
but when I edit the application's code only, then autospec doesn't run. 
Is that a normal behavior because of people fed up of autospec running 
10 times because they saved 10 different files in a row?

I am running:
- Ruby 1.8.7 patchlevel 70
- Rails 2.2.2
- rspec and rspec-rails 1.1.12
- ZenTest 3.11


Luis Lavena wrote:
> Hey Guys.
> 
> I just updated a project form 1.1.4 that was working with autotest
> 3.10 without issues:
> 
> 1) Updated spec/model/project_spec.rb and it fired only that spec.
> 2) Updated app/model/project.rb and it fired only the matching spec 
> file.
> 
> After the update of rspec and rspec-rails as plugins a few minutes
> ago, it only run the controller specs and no other. Also, it doesn't
> matter which file I change, always run the same set of controller +
> model files.
> 
> Running old "autotest" only, it happens the same.
> 
> Since the loading and matching mechanism changed a few revisions back,
> I'll like to know if someone else is facing similar situation (or I'm
> just the one with the awkward environment).
> 
> Thanks in advance,
> --
> Luis Lavena
> AREA 17
> -
> Human beings, who are almost unique in having the ability to learn from
> the experience of others, are also remarkable for their apparent
> disinclination to do so.
> Douglas Adams

On Wed, Jan 14, 2009 at 4:28 PM, Fernando Perez <lists@ruby-forum.com> 
wrote:

> I am facing a similar problem. Actually what happens, is that when I
> edit specs and then save, then autospec detects it and runs the specs,
> but when I edit the application's code only, then autospec doesn't run.
> Is that a normal behavior because of people fed up of autospec running
> 10 times because they saved 10 different files in a row?

No, that's not intended behavior.  It should be running for every
save.  How do you have your tree organized?  And are you running
autospec from the root of your project?

Peter