similar to: rspec report diffs

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

It looks to me that hpricot is a dependency to building rspec: euclid% rake pre_commit (in /Users/smtlaissezfaire/ruby/projects/rspec/hpricot) rake aborted! Could not find RubyGem hpricot (>= 0.0.0) /Users/smtlaissezfaire/ruby/projects/rspec/hpricot/rakefile:9 (See full trace by running task with --trace) Let me know if I''m wrong. Otherwise, I''ll submit a patch in the docs.

Here is the list of Ruby related projects accepted for GSoC. It includes two very similar projects (seemingly the same project, really, but I''m not saying anything ;) ) using RSpec to build a spec suite for implementations of the Ruby language: http://code.google.com/soc/ruby/about.html I''m, personally, very excited about the implications of this. Thanks to all of you who use,

Hey, I just updated from the edge and it looks like this _issue_ has resurfaced. Yesterday things were working (stories and specs). No code base changes, only rspec and rspec_on_rails After updating today I now need to set <config.txn...fixtures> to false in the spec_helper.rb to get the specs running, the stories are fine. Looks like the fixture loading is trying to start a txn. I

I''m wondering: Does it make more sense to add on successful? as an alias for success? in ActionController:TestRequest? I keep getting these two mixed up in my specs and was wondering if it would be helpful to anyone as a small patch to rspec. Best, Scott

Hi all, How can I use spec fixtures with rails integration tests ? I''ve tried adding {{ fixtures "../../spec/fixtures/myfixture" }} to the integration test but the fixtures are not loaded when I run the rake task. Rails doesn''t load symlinked fixtures either so I copied the files from spec/fixtures for the time being. Not very DRY. Any ideas ? Keith

How can I spec out a rake task? How can I use rake in my spec''s? I want to fix this rake spec:autotest bug with --drb and --color. How can I get rake output? How would I get out of autotest? My initial thought is just to run the command in the spec. Scott

I''m trolling for example RSpec code. Any pointers appreciated. Cheers, Obie

One of the links to the subversion repository is wrong. Under the heading which starts: If your own project is in Subversion and you?d like RSpec on Rails to always follow HEAD, install with -x: the second link: ruby script/plugin install -x svn://rubyforge.org/var/svn/rspec/trunk/ rspec_on_rails/vendor/plugin/rspec_on_rails should be: ruby script/plugin install -x

As it is currently, in trunk, --failures and --examples except a text file, each line containing the name of a spec. I''m wondering: Would a a patch to use YAML (instead or as well as) plain text be welcomed? I''m thinking of a yaml file like the following: spec_file_1: file: spec/person_spec.rb specs: - should have first name - should provide email address

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

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

I''m getting the following error when i either checkout or update from svn://rubyforge.org/var/svn/rspec/trunk svn: Error processing command ''mv'' in ''C:\work\rspec2\RSpec.tmbundle\Preferences'' svn: Can''t move source to dest svn: Cannot rename file ''C:\work\rspec2\RSpec.tmbundle\Preferences\.svn\tmp\text-base\Symbol List:

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

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?

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

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

Is anyone using rspec with autotest? Scott

I want to create a spec/regressions directory with various regressions (for my rails project). I tried the following: describe LoginController, "regression for user creation when steves_sister does not exist", :behavior_type => :controller do controller_name :login before :each do @params = { "commit"=>"Create Account",

Has the should_... syntax changed? I''m getting errors when running the following: should_render(:index) should_be_valid should_not_be_valid should_respond_to should_be should_render I thought the syntax changed to something like the following: obj.should render(:index) but this doesn''t seem to work. Scott