similar to: slow rails_spec

Hi, all- I started playing with RSpec in a new Rails app. I''ve installed the plugin and bootstrapped it, and run ''script/rails_spec_runner'' (not rails_spec_server as the website currently reads, btw) in a separate shell, then in another shell I run ''script/rails_spec'' and get the following: /usr/local/lib/ruby/1.8/drb/drb.rb:837:in

I installed 0.7.5 and the corresponding Rails plugin. Now it seems that the rake command is: rake spec:autotest I immediately ran into several problems: 1. rspec_autotest.rb line 30 has curly quotes and makes Ruby choke 2. Same line, rails_spec is spelled solid, when it should have the underscore But fixing these didn''t get me back going. Now I have to have a rails_spec_server

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.

rspec-rails version 1.2.0 has been released! * <http://rspec.info/> * <http://wiki.github.com/dchelimsky/rspec> * <http://wiki.github.com/dchelimsky/rspec/rails> * <http://wiki.github.com/dchelimsky/rspec/upgrades> Behaviour Driven Development for Ruby on Rails. Changes: ### Version 1.2.0 IMPORTANT INFORMATION: Due to changes in Rails-2.3, there are some changes in

Hey list, I''m trying to use the rcov integration that rspec provides in my Rails application. As per the documentation on the website, I''ve created the following rake task: lib/tasks/specs_with_rcov.rake: require ''spec/rake/spectask'' desc "Run all specs with rcov" Spec::Rake::SpecTask.new(''specs_with_rcov'') do |t| t.rcov = true

Hi, Q1 - Know why rake doesn''t recognize "rake examples_with_rcov" per http://rspec.info/documentation/tools/rcov.html ? Q2 - Also when I run "rake spec:rcov" it seems to give me the same as if I just run "autotest" or "rake spec". I was expecting a heap of pointers to code I haven''t tested?

Hi there, I''m having trouble with `rake spec:models`. It''s failing on: - 1 old rspec/rails project - all new rspec/rails projects But, it *is* working fine on my other (older) rspec/rails projects. All projects are on rspec & rails 1.0.8, Rails 1.2.3, os X ppc Here''s a fresh rspec/rails project with failing rake task $ rails test_app -d postgresql $ cd

At work we''ve got a rather complex app with both specs and tests. Our default rake task runs all our our tests and specs. We''ve also got separate rake tasks to run groups of tests and specs in the various subdirectories. The default task simply lists all the individual tasks as pre-reqs. We do a lot of branching and merging, so we really want to run all of the tests and specs

I''m using edge spec, edge rspec_on_rails, edge rails. I just switched to edge and ran the translator tool and I''m trying to get everything to pass again. One of my issues is getting render back up and working for my controller specs, here''s an example: describe "Requesting /users using GET" do controller_name :users setup do @user = mock_model(User)

I have some specs tucked away inside my vendor/plugins directory that I want to run when I run rake spec. I''ve got the rake task working just fine, but for some reason rcov seems to choke when I try to tweak the included/excluded files to ignore any files in app/ but to include files in vendor/plugins/ plugin/app/** The error I get is this: No file to analyze was found. All the

I''m just getting started with rspec, I''m running on edge for both. In a fresh project, I freeze edge, install the edge rspec plugin. I generate a simple rspec_model and run the spec. It passes. When I run rake spec:doc, I get the following output: - NO NAME (Because of --dry-run) where the specification should be. In fact if I just make a pending spec, it does the same.

With rspec 1.0.8 I can run Test::Unit tests and rspec tests using: rake default and all tests and specs run. With edge rspec the Test::Unit tests return with the message: [list of tests] Finished in 4.5e-05 seconds 0 examples, 0 failures How can I get Test::Unit and rspec to happily co-exist again? Thanks, Alvin

In my spec folder, I have a "remote" directory, which contains my specs for live data transferring with an outside api. When I run rake spec, it runs the remote specs and I don''t want it to. Keep in mind there is NO lib/tasks/remote.task file. I ONLY want these remote specs to run when I execute rake spec:remote How can I achieve this?

$ rake spec --trace (in /work/workspace/ng) ** Invoke spec (first_time) ** Invoke db:test:prepare (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:test:prepare ** Invoke db:test:clone (first_time) ** Invoke db:schema:dump (first_time) ** Invoke environment ** Execute db:schema:dump ** Invoke db:test:purge (first_time) ** Invoke environment ** Execute

Hi, We''ve been building plugins for our app, and we kept running into forgetting to run the plugin specs when we updated from svn. So, I took the task on to have the rake spec command include our plugin specs, as well. I only wanted to have our plugin specs run, not third party ones. In order to do this, I edited the rspec_on_rails /tasks/rspec.rake file to include our specs in the

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

I saw the RCov page at http://rspec.rubyforge.org/tools/rcov.html and decided to add it to my project. My rakefile looks like this: require "rake" require "spec/rake/spectask" desc "Run all specs with RCov" Spec::Rake::SpecTask.new("spec:rcov") do |t| t.spec_files = FileList["spec/**/*_spec.rb"] t.rcov = true end When I run rake spec:rcov,

I figured most of it out. The Spec::Rails stuff was something in the code which has been fixed by revision 3099. The test methods partially make sense. Since the test/unit code has been integrated, methods with test in them are automatically turned into specs. However, the test? method is in a lib file that isn''t directly loaded into the specs. It is a convenience method: def

I have just committed some changes to the spec command line addressing the following shortcomings: * drb-based spec running (fast-running rails specs) couldn''t be used from spec/rails'' rake tasks or RSpec.tmbundle * coloured or any other standard spec command line options could not be passed to spec/rails'' rake tasks These shortcomings are now history. Options can now

Hi Aslak, Thanks for the help. That bug is fixed in trunk. Here''s my path to recovery ... $ svn co svn://rubyforge.org/var/svn/rspec/trunk ~/tmp/rspec $ cd ~/tmp/rspec $ rake gem $ sudo gem install pkg/rspec-0.7.3.gem $ ./script/plugin install --force svn://rubyforge.org/var/svn/rspec/trunk/vendor/rspec_on_rails/vendor/plugins/rspec $ ./script/generate rspec (required to regenerate