similar to: autotest & rspec2

Hi all, I tried testing with Rspec for first time, following a tutorial. "rspec spec/" works fine but when I try ''autotest'' it gives me the error message below. I also made a gist about it: https://gist.github.com/779265 It seems like a redgreen or ZenTest error. I''m using Ubuntu10, Rails3, Ruby 1.9 and RVM. Any help is appriciated, thanks in advance, gezope

Hi! And now for the second part of the subject of my previous mails :) $ cat cucumber.yml default: . autotest: -v . autotest-all: -v -f progress . $ cucumber -i . -f progress PP Pending Scenarios: 1) enlightenment (meditation) $ AUTOFEATURE=true autospec # bug! prompt returns immediately, ZenTest gem not a dependency? a warning that autotest was not found would be nice. $ sudo gem

Josh Knowles http://joshknowles.com/ just let me know that ZenTest Autotest 3.50 now handles your RSpec specs. http://blog.zenspider.com/archives/2007/04/zentest_version_350_has_been_released.html That''s a great news. Josh also shared with me a quick hack to make autotest work with only the RSpec plugin installed. Add the following into your ~/.autotest file

Trying to set up a Rails 3 project with RSpec and Autotest. I followed these steps exactly: http://gist.github.com/365816 But when I start up autotest, I get: $ autotest loading autotest/rails style: Rails instead of: $ autotest loading autotest/rails_rspec2 style: RailsRspec2 And autotest doesn''t seem to do anything. Any idea what''s happening? I''m using Ruby

Hello, I have noticed that, since version 1.1.4, autotest/autospec does not run any of my specs. After getting a hint from http://b.logi.cx/2008/10/9/non-auto-spec, I dove a bit deeper into the code and found that spec is no longer being run by ruby. I monkey-patched Autotest::Rspec in my .autotest file so that spec is again executed (using code taken from version 1.1.4). autospec is now

OS=CentOS-5.2 Ruby=1.8.6 Rails=2.2.1_RC Gems all up to date I have been experimenting with autotest and I have a few questions. 1. given export AUTOFEATURES=TRUE if ./test exists (with tests) then these tests are run and the features are not. Is this intended behaviour? 2. given require ''autotest/redgreen'' in .autotest if /test tests are run then all I get colourized is a

I have the same problem with the combination above with Ruby 1.9.2 on Windows XP, as described here: http://www.ruby-forum.com/topic/205569 Calling Rspec directly produces colored output, but autotest spits out ANSI sequences. The issue was supposed to be closed with win32console 1.3.0, but obviously it didn''t for the above-mentioned combination. -- Posted via

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

autotest will no longer run my tests after I installed the rpsec gem and removed the plugins. I did install the rspec-rails gem as well. Is anyone else having this issue? -- Posted via http://www.ruby-forum.com/.

Hi all, Running on OSX 10.5.3, Latest Rspec trunk, Rspec rails trunk, latest autotest gem and rails 2.1 I''ve lost my colour output in autotest. rake spec gives colour output, but autotest gives me black and white. It was working a little bit before, I think I upgraded to the latest versions of everything to get all the textmate snippets talking and being friendly to one another again

Hi guys, I am having a problem with autospec. I upgraded to rspec-1.2.6, then I tried to run my specs with autospec. All my specs passes (green), until here, that''s all ok. The problem is that after all my specs have passed, the autospec stops, I mean, it doesn''t continue to run on background. The same behavior happened if one of my specs fails too. Is this the current default

I have the following code, which yields instance eval''s the block given: class Foo def bar(&blk) instance_eval &blk end def baz yield end end The effect of this is that self is reassigned: Foo.new.bar do # here, self is the instance of Foo # created by new end But normally self is the object in which Foo.new.bar {...} occurs. Foo.new.baz do

Hello, I have a Rails3beta4 project where I want to use rSpec stubs in a Cucumber feature. Unfortunately it looks like requiring ''spec/stubs/cucumber'' in env.rb does not work anymore: I get a "no such file to load -- spec/stubs/cucumber (LoadError)" error. Is it possible to use rSpec stubs in Cucumber with rSpec2? If not, is there any other viable alternative? Thanks

Hi folks, I''m going through railstutorial.org and so I apologize if I''m hitting the wrong group here and would appreciate any appropriate redirection if necessary. I''ve set up Spork + Autotest as per Michael''s instructions in http://ruby.railstutorial.org/chapters/static-pages#sec:testing_tools Essentially by doing the following (using rvm & I''m

People, I''m trying to run autotest on rails 2.3 I get a NoMethodError. Here is what I see: Sat Mar 21 20:47 /b/tmp/myfc23 maco$ Sat Mar 21 20:47 /b/tmp/myfc23 maco$ autotest loading autotest/rails_rspec ./vendor/plugins/rspec/lib/autotest/rspec.rb:24:in `initialize'': undefined method `failed_results_re='' for #<Autotest::RailsRspec:0x1205b88> (NoMethodError)

When an autotest finishes running, then the output for the qemu logfile in /var/log/libvirt/qemu/ is added to the output. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- autotest.sh | 14 +++++++++++++- 1 files changed, 13 insertions(+), 1 deletions(-) diff --git a/autotest.sh b/autotest.sh index 7503be0..5ccdbbb 100755 --- a/autotest.sh +++ b/autotest.sh @@ -41,8 +41,9 @@

Hi, When I start the "autotest" it gives me the following error...not sure what HOME path I have to set...all Ruby/Rails related components are in path! --- C:\>autotest -rails C:/Tools/InstantRails/ruby/lib/ruby/gems/1.8/gems/ZenTest-3.3.0/lib/autotest.rb:285:in `expand_path'': couldn''t find HOME environment -- expanding `~/.autotest'' (ArgumentError) ---

Not sure if anyone needs this, but I have successfully been running rspec/trunk with autotest for a few days now on a non-rails project. The process is pretty simple: 1. Put rspec into vendor/plugins/rspec (on externals, or simply frozen) 2. Add autotest/discover.rb: Autotest.add_discovery do "myproj" end 3. Add autotest/myproj.rb: require File.dirname(__FILE__) +

I''m having trouble getting autotest to run "out of the box" with rspec. I''ve got a Leopard setup with Zentest 3.5.0, rspec on trunk, and rails 2.0PR. No ".autotest" file. There are a couple of issues: 1. Running ''autotest'' inititally yields a command not found for "spec --diff unified etc etc". This seems to be an old issue but

Hello, I''ve been trying to google the definitive way to combine autotest, rspec, and spec-server, but to no avail. It seems like there are lots of suggestions from old versions. Furthermore, some commands such as rake:autotest don''t seem to be around anymore. So, is it required to install ZenTest as a gem? I have version 3.9.1. I believe this gets me the autotest