similar to: Specs with -X fail

My specs are still taking to long to run in a rails app. Is anyone using an in-memory database to run their specs? Any pointers or tips? Scott

I''ve been seeing the following in some of my view specs: .P.P........ignoring attempt to close spec::mocks::mock:0x7334c4c with td opened at byte 258, line 20 closed at byte 287, line 20 attributes at open: {} text around open: "\t</tr>\n\t<tr>\n\t\t<td>#<Spec::Mocks::Mock:0" text around close:

At times I''ve gotten the message "No Server Running" from drbspec with my rails app. The thing is, the drb server certainly is running! This happened a few times with my model specs. I''m not sure exactly what the problem was there - I believe I was loading up fixtures that didn''t exist. I was calling fixtures :singular_table_name as opposed to

How would you spec out something like the following: def a_method x = Class.new do include Enumerable end # do something here with x end describe "The Anonymous Class" do before :each do @anonymous_class = mock Class Class.stub!(:new).and_return @anonymous_class end it "should create a new anonymous class" do

What is the appropriate way to stub out (and put an expectation on Object#__send__), without getting warnings from the Rspec mock library? Scott

Is there some way to remove the database hit when running rake rspec:models ? I''d like to mock all of my objects (or at least remove all reliance on fixtures and the database itself) - both for speed and because static fixtures are brittle. Best Regards, Scott Taylor

Hi there, I can''t seem to access the fixture name as a class variable from my specs. I have to set the variable in the spec setup. ... [fixtures] my_fixture: id: 1 ... [rpsec] @my_fixture.id.should == 1 ... [error] You have a nil object when you didn''t expect it! The error occurred while evaluating nil.id ... [my setup] RSpec-0.7.5.1 (r1395) - BDD for Ruby Rails

I have looked through the docs, looked at the code, even gave a cursory (2 page) glance at google, and it is not clear to me what SpecServer is or what it is for. Is it meant to speed up the execution of specs in a rails environment by doing some magic on the database? Or I am thinking it keeps a copy of Rails running to avoid the rails reload delay... Is there any documentation on this so I

I find myself doing this kind of thing a lot in Controller Specs: @vacancy = mock_model(Vacancy) @vacancy.stub!(:reference) @vacancy.stub!(:title) @vacancy.stub!(:created_at) @vacancy.stub!(:updated_at) @vacancy.stub!(:body) @vacancy.stub!(:contract) @vacancy.stub!(:location) @vacancy.stub!(:salary) @vacancy.stub!(:benefits)

Just wanted to pick some smart people about this topic: What are you guys doing to increase the speed of your specs? I''m a big fan of autotest, but right now my current project has 438 specs (for rails). Most of them are in the model, and for all of them we are hitting the database (they are more functional specs than unit-tests). The whole suite takes 112 seconds (meaning the

I''m trying to use it_should_behave_like, and something seems to be wonky with the syntax. When I add :shared=>true, the DSL complains that the next line is the fixture declaration: /vendor/plugins/rspec/lib/spec/dsl/behaviour_eval.rb:137:in `method_missing'': undefined method `fixtures'' for #<Spec::DSL::EvalModule:0x324a2cc> (NoMethodError) Here''s the

Is it a bad practice to use a subversion repository to the trunk of rspec and rspec_on_rails? Or rather, is it doomed to fail, since my gem will always be out of date? I know I can''t use spec, installed from gem,s if I have the latest revision of rspec and rspec_on_rails checked into my plugins directory. But I should still be able to use it with the --drb option, correct?

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

I am having inconsistent output with multiple options in the spec.opts file. I can, for instance, pass --color or --colour, or, separately, use --drb. But when combining them I get: /opt/local/lib/ruby/1.8/optparse.rb:1381:in `complete'': invalid option: --options --color --drb (OptionParser::InvalidOption) from /opt/local/lib/ruby/1.8/optparse.rb:1379:in `catch''

What is the difference between these two ways of mocking (with and without the string): mock(''Object'') and mock(Object) ? Scott

Hello, As I''m becoming more and more familiar with mocking/stubbing, I''m going back to some of my model specs and revaluating how I wrote them. I have certain models in which validation requires the presence of an associated model, which itself needs to be valid(validates_presence_of and validates_associated). When I wrote the specs, I wrote helpers for the attributes instead

Hi all, I feel like I''m missing something really easy and I''m just not seeing it. I''m using the restful_authentication plugin and have a User model. Uesr has_many :things and Thing belongs_to :user. That''s it. I did a "script/generate rspec_scaffold thing" to generate all the necessary bits. The "rake db:migrate" to create the db. At

Mocha''s mock/stub framework has the ability to stub all methods on a mock given. Does RSpec''s mocking framework have this ability? And if not, is there some reason it shouldn''t be implemeneted? Regards, Scott

Hi all, Initially I thought this was a bug in the built-in mocking framework(and it still may be), but I better hash it out on the mailing list before I file/reopen the ticket: http://rspec.lighthouseapp.com/projects/5645/tickets/478-mocks-on-constants#ticket-478-6 I thought my example illustrated my problem, but obviously I was passing the wrong arguments to the mock. I revised my example to

Here is an example from autotest: class Autotest def self.run new.run end def new ... end def run ... end ... end How would I spec out Autotest.run? Two complications come to my mind: 1. How do I spec out class methods? (please point me to docs, if any. I can only find class level specing on "partial mocks" (of rails class objects) 2. How can I tell