similar to: rspec_on_rails, receive_and_render experiment

In 1.0.8 I am able to nest describe blocks, but in moving to trunk, revision 2971, I am unable to have the expected results. Here is an example nested describe block: describe "foo" do describe "with no arguments" do before do puts "a" end it "should" do puts "SHOULD" end end describe "with invalid

I just downloaded rspec_on_rails-1.1.3.tgz onto a mac on OSX 10.4 and another computer (Ubuntu 7.10) and I get the same tar errors when I try to decompress: rspec_on_rails-1.1.3/spec_resources/views/view_spec/implicit_helper.rhtml rspec_on_rails-1.1.3/spec_resources/views/view_spec/multiple_helpers.rhtml gzip: stdin: decompression OK, trailing garbage ignored

Hi there, I''ve installed rspec, rails plugin & generators thusly: $ sudo gem install rspec $ sudo gem install rspec_generator $ sudo gem install zentest -v 3.4.1 $ ./script/plugin install svn://rubyforge.org/var/svn/rspec/tags/REL_0_7_2/vendor/rspec_on_rails/vendor/plugins/rspec $ ./script/generate rspec $ ./script/generate rspec_model ModelName With Rails version: $ rails

Hi there, I''ve installed rspec, rails plugin & generators thusly: $ sudo gem install rspec $ sudo gem install rspec_generator $ sudo gem install zentest -v 3.4.1 $ ./script/plugin install svn://rubyforge.org/var/svn/rspec/tags/REL_0_7_2/vendor/rspec_on_rails/vendor/plugins/rspec $ ./script/generate rspec $ ./script/generate rspec_model ModelName With Rails version: $ rails

In my rspec_on_rails controlle rspec, I have this: require File.dirname(__FILE__) + ''/../spec_helper'' describe FooController, "with a foo" do it "should be false" do get ''index'' assigns[:foo].should be_false end end In my controller I have this: class FooController < ApplicationController def index @foo = FALSE end

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

Hey, I''m using rspec and rspec_on_rails to test some RSS feed views, the problem is that the specs spew out messy warnings when they run: ignoring attempt to close channel with link opened at byte 61, line 3 closed at byte 141, line 5 attributes at open: {} text around open: "ss version=\"2.0\">\n <channel>\n <title" text around close:

Last night it seemed like the mailing list was playing catchup, as I got a flood of emails from the past few days. Has anyone else seen this? -- Zach Dennis http://www.continuousthinking.com http://www.mutuallyhuman.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20081030/f19f3755/attachment.html>

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've having trouble downloading and compiling Xapian 1.0.19 on OSX 10.5.8. Does the below error look at all familiar to anyone? creating bin/quartzcheck g++ -DHAVE_CONFIG_H -I. -I./common -I./include -I./backends/quartz -Wall -W -Wredundant-decls -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long -Wformat-security -fno-gnu-keywords -Woverloaded-virtual -Wundef -Wshadow

I posted a ticket to lighthouse: http://rspec.lighthouseapp.com/projects/5645-rspec/tickets/595-deprecate-integrate_views Please put your comments and thoughts there, as that is the best place for that discussion. I wanted to make it more "visible" so it could get wide community participation in case there are folks who absolutely feel integrate_views is necessary (considering that we

Hi all rspec_on_rails/lib/spec/rails.rb starts: ------ dir = File.dirname(__FILE__) require ''application'' silence_warnings { RAILS_ENV = "test" } ------ That force into "test" environment is causing me trouble and I''ve commented it out. Why? I''m testing a plugin, and have a sort of mini rails app that I use for the specs. The

I ran into something really puzzling today. I don''t know exactly why it''s happening, but I thought I''d share my experiences. I started a dummy app just to test an idea outside of the context of my real work today. So, I quickly get things started: * rails junk * cd junk * ruby script/plugin install svn://rubyforge.org/var/svn/rspec/tags/ CURRENT/rspec * ruby

hi all I''m still a little uncertain on how to use mocks/stubs with rspec when dealing with associations. I know the point is to isolate the code being tested and remove external dependencies, but I''m not sure how to implement it. Can someone suggest how they would spec the code below: I have a Book model and Review model class Book < ActiveRecord::Base has_many :reviews

After a couple of quick fixes this morning, rspec_on_rails (in trunk as of rev 3070) now works correctly with Rails 2.0.1 Now that Rails 2.0 is out, we''ll try to get an RSpec 1.1 release candidate out the door in the next few days. Cheers, David

Hello rspec-users, I''ve encountered a strange bug in rspec, but it may be me who is wrong. I''m running latest version from the trunk (r1678) of both rspec and rspec_on_rails. Please consider the following model: class Url < ActiveRecord::Base def after_save Contact.create!(:primary_email => ''user at example.com'') raise

I''m heading out of town, but had a quick thought I wanted to share. Rather then using ambiguous named request helpers in controller specs like "do_request", I''ve been using more readable helpers like "post_create". For example... describe ProjectController do def post_create post :create, ... end before do end it "creates a new

In rspec_on_rails, the spec:doc task uses --dry-run, which doesn''t jive well with rspec''s ability to write docs for you. For example, I use the rspec_expectation_matchers plugin from spicycode.com (scanned for a name, didn''t find one =), and end up writing specs like: it { @ticket.should validate_presence_of(:name) } Which results in specdocs such as: Ticket

Does anyone else have issues running rspec textmate bundle? I''ve got revision 2997, but the blasted thing just won''t run. It is checked out to my /Users/zdennis/Library/Application Support/TextMate/Bundles/RSpec.tmbundle When it runs I get the below error... "textmate" is not a valid class name

As I think I previously mentioned, there is an incompatibility with rails 1.2.1 and sqlite3 3.3.8. see: http://weblog.rubyonrails.org/2007/1/29/using-sqlite3-with-rails and: http://weblog.rubyonrails.org/2007/2/6/rails-1-2-2-sqlite3-gems- singular-resources Sqlite is now at 3.3.13. Because of this, if a developer is trying to create a patch for rspec_on_rails, he will have one of the