similar to: spec_server doesn''t update ''required'' files

hi all I''m seeing strange behaviour when running specs using spec_server. They take longer to execute, and it looks like none of examples are being run. here''s the output for a simple spec file using just the spec command: ---------- foo at holly:~/rails/allison$ time ruby/script spec spec/models/listing_spec.rb ...... Finished in 0.060469 seconds 6 examples, 0 failures <

hi all I''m trying to use spec_server to run my specs in rails, but the specs don''t seem to be running any faster, and it looks like they''re being run twice when I use the --drb option ..? The app I''m testing is just a basic rails app with 2 empty models and a hello world controller. The specs are just the default ones created by the generators. I was

Hey guys, I''m running spec_server and using --drb with my specs in Rails, and I''m seeing virtually no speed up. I''m using rspec/rspec_on_rails trunk. Is there something I''m doing wrong? TIA, Jeremy -- Jeremy Stephens Computer Systems Analyst I School of Medicine Department of Biostatistics Vanderbilt University

Hello, Running RSpec without DRB works fine. However, "spec -X" runs without error but provides no output at all, even though the DRB spec_server seems to be fine. Has anyone got some suggestions as to why and how to fix? RSpec: 1-1-0RC1 build time 20071212145122 RSpec on Rails: Build time 20071212145122 Ruby: 1.8.6 Rails: 2-0-1 Win XP SP 2 Thanks very much, Dave -------------- next

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

Is the rspec_autotest plugin mentioned here, http://blog.nicksieger.com/articles/2006/11/15/rspec-autotest-now-a-rails-plugin the accepted method of auto testing specs? It''s an old article, and after grabbing the plugin, and giving it a run, it fails with: $ rake spec:autotest:rails trunk/vendor/plugins/rspec_on_rails/lib/spec/rails/dsl/behaviour/rails_example.rb:31: undefined method

Is there something currently going on on the rspec trunk that causes a massive slowdown when running rake spec and autotest (without spec_server)? I updated to the latest trunk yesterday and the time needed to run the specs of my app jumped from ~20 seconds to more than a minute. The weird thing is that if I run the rake spec tasks separately (controllers, models, views, helpers), they

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

Hi everyone. I can''t get the above(subject line) combination to work. If I use a standard sqlite3 file db for the test db, and spec_server all the specs on my models pass. If I use an in-memory db for the test db, script/spec w/o spec_server, they all pass. But if I use in-memory and spec_server I get the following error: 1) ActiveRecord::StatementInvalid in ''User should be

hi all a few days ago i reported spec_server didn''t appear to be running specs and the command itself was running slowly. I''ve since tried it on a new system with a clean install of ubuntu 7.04, rails 1.2.3 and rspec 1.0.2 and I''m seeing the same behavior. *** without spec_server *** x at holly:~/rails/test$ time ruby script/spec spec/models/user_spec.rb . Finished in

Just ran svn up this morning, and got this (after running ./script/ generate rspec) escher: ./script/spec spec/models/item_spec.rb Finished in 8.0e-06 seconds 0 examples, 0 failures ./script/spec:4:in `run'': wrong number of arguments (3 for 1) (ArgumentError) from ./script/spec:4 Using rails 1.2.3, rspec trunk, on Mac OS X.4.9. Any ideas, or is this a bug in

Hey all - The trunk currently supports three types of mocking/stubbing: Mock Objects (created dynamically at runtime) Partial Mocking of methods on existing classes Stubbing of methods on existing objects or classes The main difference between Partial Mocking and Stubbing is that Stubs don''t verify. I''m wondering if we really need the stubbing facility at all, given that we

I had posted this on the regular Rails list, but upon trying this in script/console, it seems like the behavior only exists when running rspec. I''m getting some weird behavior in one of my models. I have a model defined something like this class User < ActiveRecord::Base attr_accessor :password validates_presence_of :password end If I validate the model without specifying a

I''m trying to write some tests for the ApplicationController as shared tests that can be run in all of my other controller tests, but am getting a nil.rewrite error. Below is what I have... describe AccountController do it_should_behave_like ''Application controller'' end describe ''Application controller'', :shared => true do it

I''d like to start gathering information/debating on the advantages/disadvantages of using it "should ..." vs other techniques. Dan North explained why we should use should: http://dannorth.net/introducing-bdd/ I used to use it "should ..." for the projects I was on, until I was challenged by a fellow developer who started using it with an active voice. For example

Seems like the recently updated (and wonderful) textmate bundle does not take into account running individual tests that are in nested specs. Anybody else notice this? Any ideas? Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rspec-users/attachments/20080113/15d5cc2f/attachment.html

Hello, I''m scheduled to give a rspec brown bag this Wednesday (11/22) for my company (Pivotal Computer Systems, http://www.pivotalsf.com). I did see Dave Astel''s talk as well as several of my coworkers. The developers at my workplace are experienced Agile developers. What would be some good things to focus on for this brown bag? Are there slides to presentations that would be

Should the stories dir be located on the project root? I was expecting to find it located under spec/ but there isn''t anything there, just the stories dir off of /. Also there don''t appear to be any rake tasks for stories, nor generators. Should there be any? Thanks, Steve

Is anyone out there writing specs to check attr_accessible fields? I had originally written my spec to check for allowing the desired fields, and then none of the other regular db fields. Unfortunately this isn''t satisfactory, because attr_protected could have been used instead, which of course wouldn''t prevent mass assignment to any whatever=(val) method. I''m thinking

Hey guys, Does anyone have any wisdom to share on the subject of speccing Rails layouts? Most of it''s plain old view specs stuff, but are there sensible ways to verify things like the yield call? (Mocking doesn''t catch that) Thanks, Matt -- Matt Patterson | Design & Code <matt at reprocessed org> | http://www.reprocessed.org/