similar to: Autospec does not work w/ cucumber features?

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

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

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

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

Railsters: Despite Rails being the only Web platform designed for TDD, a lot of its test infrastructure is still "cargo cult" - imitating other test rigs instead of understanding their principles. Most importantly, tests should run instantly. There''s no excuse for breaking this rule, and if you invent a platform that can''t obey it then you are doing something

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

RSpec-1.1.3 has been released. If you''re using RSpec and autotest, you''ll have to upgrade to RSpec-1.1.3 and ZenTest-3.9.0 at the same time. == Version 1.1.3 Maintenance release. * Tightened up exceptions list in autotest/rails_spec. Closes #264. * Applied patch from Ryan Davis for ZenTest-3.9.0 compatibility * Applied patch from Kero to add step_upcoming to story listeners.

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

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

When I work with a .html.erb file, the autotest rspec on rails stuff doesn''t understand the file to map it to the right test. I wanted to submit a patch for this, but I''m unsure where the specs would be to update. I found the necessary mapping in rspec_autotest.rb, but I can''t find any specs anywhere. Help? I just need to have /app/views/coupon/index.html.erb to map to

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

Hey all, I have a spec that is hanging when it is running. How do I get the rspec runner to show what specs it''s running so I can which one is hanging? I am calling the runner from my rails project. Thanks, Ben

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/.

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

Yes, slides will be available afterwards. Additionally, a very similar talk will be presented at SCALE this year as well. Do you have any more info about how tinc is used by NYC mesh? Ben On Sun, Nov 15, 2015 at 3:55 PM, Daniel J. Grinkevich < danielgrinkevich at gmail.com> wrote: > Will the slides be posted after the talk? > > We use tinc for NYC Mesh to connect nodes that do

http://bugs.freedesktop.org/show_bug.cgi?id=19450 Summary: 6600GT on G5(Dual Head) - Pointer to flat panel table invalid Product: xorg Version: 7.2 Platform: PowerPC OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo:

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! Just wrote a few stories and committed code to a project of mine, then realized I made a mistake (with the commit, not the code or tests). It would be nice to put the script that runs the stories as a pre-commit hook, preventing the commit from succeeding if the stories fail. For that, I need to set the right exit code. In turn, I need to know he result of the tests. Given the

Hi tincfolks, I'd like to announce that we're planning a talk [1] about tinc and some of the uses that we've developed for it. It'll be given at FOSSETCON 2015 [2] in Orlando, Florida on Nov 19-21. If anybody is in the area, please consider attending. Ben [1] http://www.fossetcon.org/2015/sessions/secure-peer-networking-tinc [2] http://www.fossetcon.org/ -------------- next part

I was looking over some of my specs. I was thinking that the following: @game.should_receive(:name).and_return(''The Battle for Blaze'') @game.should_receive(:people).and_return(5000000) @game.should_receive(:activated).and_return(true) Would it look cleaner if I could do this instead? @game.should_recieve_and_return( :name => ''The Battle for Blaze''