Not running correct specs under autotest:

I know this isn’t autotest-users but I’m not sure where else to bring
this up:

[[“app/controllers/contents_controller.rb”, Wed Jun 04 14:11:03 +0100
2008]]
[[“app/controllers/contents_controller.rb”, Wed Jun 04 14:11:03 +0100
2008]]
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby -S
script/spec -O spec/spec.opts spec/models/user_spec.rb

I had saved ‘contents_controller.rb’ but it did not decide to re-run
the ‘contents_controller_spec.rb’ only ‘user_spec.rb’ (which has a
failing spec so is probably held over from the previous runs). If I
ctrl+c to run all specs it runs the controller spec again. If I resave
the controller the change is again detected but the spec is not run.

I’m using Rails 2.1, edge rspec & rspec-rails, and ZenTest 3.9.2

Anyone else seen this?

Matt.

On Jun 4, 2008, at 8:15 AM, Matt M. wrote:

I had saved ‘contents_controller.rb’ but it did not decide to re-run
the ‘contents_controller_spec.rb’ only ‘user_spec.rb’ (which has a
failing spec so is probably held over from the previous runs). If I
ctrl+c to run all specs it runs the controller spec again. If I resave
the controller the change is again detected but the spec is not run.

I’m using Rails 2.1, edge rspec & rspec-rails, and ZenTest 3.9.2

Anyone else seen this?

This just got fixed a few hours ago. Grab the latest from git://
GitHub - dchelimsky/rspec: Behaviour Driven Development framework for Ruby.

Cheers,
David

On Wed, Jun 4, 2008 at 2:18 PM, David C. [email protected]
wrote:

This just got fixed a few hours ago. Grab the latest from
git://github.com/dchelimsky/rspec.git.

Edge moves fast, I only installed it 3.5hrs ago :wink:

Keeping up is awkward because my project is currently still using
Subversion and I’ve not found a good way of managing Git externals in
this setup.

Another argument for switching the project to Git I guess…

Thanks David.

M.

On Wed, Jun 4, 2008 at 2:18 PM, David C. [email protected]
wrote:

This just got fixed a few hours ago. Grab the latest from
git://github.com/dchelimsky/rspec.git.

It’s not fixed for me. My copy of rspec was installed after the commit
that closes #369.

regards,

Matt.

On Wed, Jun 4, 2008 at 2:18 PM, David C. [email protected]
wrote:

/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby -S
Anyone else seen this?

This just got fixed a few hours ago. Grab the latest from
git://github.com/dchelimsky/rspec.git.

Your last fix does seem to have fixed the problem of getting
ActiveRecord::Base not found, etc… which was due to autotest running
the controller or model as a spec.

This problem is different, it’s reporting that the controller has
changed but not running the associated spec.

Hope that helps.

Matt.

On Jun 4, 2008, at 8:33 AM, Matt M. wrote:

On Wed, Jun 4, 2008 at 2:18 PM, David C.
[email protected] wrote:

This just got fixed a few hours ago. Grab the latest from
git://github.com/dchelimsky/rspec.git.

Edge moves fast, I only installed it 3.5hrs ago :wink:

I wish it moved faster - this one’s been sitting around for a bit.

Keeping up is awkward because my project is currently still using
Subversion and I’ve not found a good way of managing Git externals in
this setup.

Rails 2.1 supports plugins from git. Are you using an older version of
rails (come on - 2.1 has been out for 3 days already!). If you are,
just follow directions at GitHub - dchelimsky/rspec-rails: RSpec extension library for Ruby on Rails
wikis.

Cheers,
David

On Wed, Jun 4, 2008 at 3:06 PM, David C. [email protected]
wrote:

I wish it moved faster - this one’s been sitting around for a bit.

:wink:

Rails 2.1 supports plugins from git. Are you using an older version of rails
(come on - 2.1 has been out for 3 days already!). If you are, just follow
directions at Home · dchelimsky/rspec-rails Wiki · GitHub.

Yep 2.1 and I used script/plugin to install from git this time. That’s
new again to me since I’ve been using piston for quite a while (or
submodules with a git based project). The new, git compatible,
“script/plugin update” takes care of the details?

M.

On 4 Jun 2008, at 15:14, Matt M. wrote:

On Wed, Jun 4, 2008 at 3:06 PM, David C.
[email protected] wrote:

Rails 2.1 supports plugins from git.
Yep 2.1 and I used script/plugin to install from git this time. That’s
new again to me since I’ve been using piston for quite a while (or
submodules with a git based project). The new, git compatible,
“script/plugin update” takes care of the details?

AFAIK it doesn’t – script/plugin install from a git URL is no better
than manually unpacking the tgz into vendor/plugins, i.e. completely
useless. I’ve pretty much resigned myself to just blowing away each
plugin directory when I want to update it, and either tracking my
local changes manually (i.e. maintaining a diff that I laboriously
reapply after updating) or monkeypatching plugins in lib/ rather than
modifying them directly.

(script/plugin update relies on svn:externals.)

Rails dependency management is getting worse. Maybe piston 2.0, with
git support, will make it better again?

Cheers,
-Tom

On Jun 4, 2008, at 9:14 AM, Matt M. wrote:

follow
directions at Home · dchelimsky/rspec-rails Wiki · GitHub.

Yep 2.1 and I used script/plugin to install from git this time. That’s
new again to me since I’ve been using piston for quite a while (or
submodules with a git based project). The new, git compatible,
“script/plugin update” takes care of the details?

I haven’t tried update (I usually run a bash script to update from my
local repo - I pretty much always have the latest).