similar to: [Rspec] Problems with autospec

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

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

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

I am trying to install rspec for rails and have the following gems install C:\INSTAN~3.0-W\rails_apps\katai>gem list --local *** LOCAL GEMS *** actionmailer (2.3.4, 2.0.2) actionpack (2.3.4, 2.0.2) activerecord (2.3.4, 2.0.2) activeresource (2.3.4, 2.0.2) activesupport (2.3.4, 2.0.2) authlogic (2.1.2) autotest-rails (4.1.0) builder (2.1.2) capistrano (2.5.9, 2.1.0) cgi_multipart_eof_fix

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 guys, I''m trying to find some information on how to get autotest to run the rspec2 tests. I have my project setup so "rake spec" runs the specs properly, but autotest seems to ignore/don''t know that there are specs to test. I read on the rspec2 wiki that autotest integration is o be added eventually. Any ideas on how to achieve this? Thanks, Jeroen

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

rspec version 1.2.0 has been released! Behaviour Driven Development for Ruby. Changes: ### Version 1.2.0 WARNINGS: * If you use the ruby command to run specs instead of the spec command, you''ll need to require ''spec/autorun'' or they won''t run. This won''t affect you if you use the spec command or the Spec::Rake::SpecTask that ships with

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

As I work with Rails TestUnit tests I am reconsidering how to use cucumber features. It seems to me that it might be best to have a coherent view of how to arrange my test suites before I get much further into this. Now, so far I have considered three possibilities: 1. Use features exclusively. Create a feature file for each model, one for each controller and possibly an additional one for

If I got this to work, do you think we could/should check in rspec_autotest into rspec? I''ve updated rspec_autotest abit, so let me know if you''d like the modified code. Scott

The latest release of Autotest, bundled in ZenTest 3.5, now has support for running specs! No longer do we need to use the rspec_autotest plugin, now it-just-works. The only problem is that the script is assuming you have the rspec gem installed. If you''re keeping up with Edge RSpec on your Rails project you''ve probably just included rspec and rspec_on_rails into your

Hi friends, I have installed and used RSpec many times before. After a long time, I am back to RSpec and I tried installing this gem. But am not able to install it. Following are the details: $ gem install rspec ************************************************** Thank you for installing rspec-1.3.0 Please be sure to read History.rdoc and Upgrade.rdoc for useful information about this

How would you spec out a call to Signal.trap (a ^C or a unix SIGINT)? Scott

Hi all, We''re thinking about retiring the test2spec translation tool because it''s becoming a maintenance problem. Is anyone using it? Would anyone miss it if it went away? Aslak

Hi, I ran in trouble with unexpected rollbacks using cucumber 0.3.0. My feature-file looks like Scenario: Create Valid Item Given I start and the step is Given /^I start$/ do get "/items" end In my log/test.log I get SQL (0.2ms) SET NAMES ''utf8'' SQL (0.2ms) SET SQL_AUTO_IS_NULL=0 SQL (0.1ms) BEGIN Processing ItemsController#index

rspec-rails version 1.2.9 has been released! * <http://rspec.info> * <http://rubyforge.org/projects/rspec> * <http://github.com/dchelimsky/rspec-rails> * <http://wiki.github.com/dchelimsky/rspec/rails> * <rspec-devel at rubyforge.org> Behaviour Driven Development for Ruby on Rails. Changes: ### Version 1.2.9 / 2009-10-05 * enhancements * added route_to and

Hi All I have setup a new dev system running LinuxMint 9 (Ubuntu 10.4). Running ruby 1.9.2, rails 3.0, RVM etc. One issue I have run into is that I can''t stop webrick with ctrl+c or ctrl+d and killing the terminal always leaves a stranded ruby process. Has anybody else run into this? Btw, webrick gets started by running "rails s" in. Also, ctrl+c works fine to stop a

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 am attending a training course covering rspec. I am using a MS WinXPpro SP3 machine. I have installed the cygwin environment. I am using git 1.5.4. I am using ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32] and rails 2.0.2 (albeit rails 2.1.0 is installed as well) I had to install rspec-rails and rspec via git and as a gem. Problem 1. If one goes to the rspec.info website and links