similar to: RSpec, TestUnit, Cucumber and Autotest

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

Hey all, Does anyone know how to disable the cucumber autotest support on a project? With this commit: http://github.com/aslakhellesoy/cucumber/commit/93470e2580b5e3cfe0c8eb3fce86e21bf8afa219 The cucumber features are worked into the autotest cycle automatically. This is cool, but on some projects I don''t think it fits well with my red->green->refactor cycle. Any ideas on

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

Hey guys After hours of hard work I finally managed to set up my development environment to run cucumber scenarios using autotest and selenium. What''s a bit bugging is the fact that Firefox always jumps to the foreground when Autotest does its job. How can I keep Firefox in the background so that I can continue with my work without being interrupted? Thanks! -- Posted via

When running autotest with AUTOFEATURE=true, all of my specs and features run fine. However, if I have a feature containing a scenario that fails, autotest lists that feature, but then returns "0 scenarios", and then runs all of the features again. Any idea why this might be? Best, Tom -- Posted via http://www.ruby-forum.com/.

I am working on my first Rails BDD project with extensive tests since starting out with Rails a few years ago. Running RSpec or Cucumber is really slow. I''m using Rails 3 and RSpec 2. To run one model spec with only 5 tests takes almost 1 minute! When it finishes it says it took only 0.9 seconds to run the actual test. So obviously it is loading the environment that takes so long. I just

I am trying to get a customized rcov rake task working. What I have so far looks like this: desc "Rcov code coverage reports" require ''rcov/rcovtask'' require ''spec/rake/spectask'' require ''cucumber/rake/task'' task :rcov => "rcov:all" namespace :rcov do Rcov::RcovTask.new(:all) do task :rcov =>

I like Shoulda. Sometimes I like plain old Test::Unit. Cucumber gives me a different thought process. I''d just like to hear some thoughts on why RSpec? What does it buy me that I can''t get with Shoulda? I just can''t seem to think in RSpec. Where is there a good example of RSpec tests that will help me grasp the right path? Thanks! -- Amos King

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

Running: Rails 3.0.5 ZenTest 4.5.0 autotest (4.4.6, 4.3.2) autotest-fsevent (0.2.5, 0.2.2) autotest-growl (0.2.9, 0.2.4) autotest-rails (4.1.0) autotest-rails-pure (4.1.2, 4.1.0) cucumber (0.10.2) cucumber-rails (0.4.0) spork (0.9.0.rc4) Gives me a truly bizarre situation. When I touch my features file, autotest runs a single, unrelated rspec test. Cucumber alone or with spork gives me the

On Thu, Nov 27, 2008 at 4:28 PM, Aslak Helles?y <aslak.hellesoy at gmail.com>wrote: > When (if) this thread ends, let''s start a discussion about indentation > conventions! > Oh... let the pleasure be mine!... and why wait? _EVERYONE_ knows that the only way to indent ruby code is 2 plain spaces. Tabs are known to be the source of all evil and 4 spaces obviously wastes

My autotest runs but when I make changes to a spec it doesn''t reload. I checked another application I was building that had 1.0.9 but it was reloading fine. How would I debug a problem such as autotest not reloading? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rspec-users/attachments/20070930/6be7160d/attachment.html

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, 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) ---

Just upgraded to latest rails and rspec builds and my autotest doesnt work undefined method `before'' for Spec::Rails::DSL::RailsExample:Class (NoMethodError) Here''s the full trace: http://pastie.caboo.se/112754 Any ideas? -- Posted via http://www.ruby-forum.com/.

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

Hello, I''m running AutoTest with Rspec on a Rails application. Every 20 or so runs I get "stack level too deep" on one particular controller stub. Ex. controller.stub!(:login).and_return(true) This particular line is in a before block of a certain describe block. The strange thing is, every single spec in this file fails on that one line, even the specs in other describe

False Positives I just discovered how easy it was to create a false positive when I, trying my first RSpec test, did this: ob.should eql?(''foo'') instead of: ob.should eql(''foo'') or: ob.should == ''foo'' As far as I can see, this is roughly equivalent to: ob.should false Neither eql?(''foo'') nor false causes the spec

I believe for rails projects you can put rspec''s code repos into vendor/plugins, and autotest will automatically use the rspec binary in that directory, and not the gem installed. Is there an easy way to do this for non-rails projects? There are a few advancements on trunk which I would like to take advantage of. Tips welcome ; ). Scott Taylor

I am using latest version for rspec-rails, ZenTest. I am getting following error, when ever I try to run autotest. Please help -head at mhart6/gems/ZenTest-4.6.2/lib/autotest.rb:315:in `load'': /Users/ jayparteek/.autotest:7: invalid multibyte char (US-ASCII) (SyntaxError)