shared examples with a block for expects?

Hi,

Basically I want to do something like this:

describe FancyThingsController do

  def do_new
    get :new
  end

  def do_create
    post :create, :fancy_thing => { :some => "params" }
  end

  shared_examples "an access controlled action" do |expectation|
    it "denies access" do
      expect(&expectation).to raise_error(CanCan::AccessDenied)
    end
  end

  describe "#new" do
    it_behaves_like "an access controlled action", proc { do_new }
  end

  describe "#create" do
    it_behaves_like "an access controlled action", proc { do_create }
  end

end

received unexpected message :id= with (20)

Please help me to understand this error message:

 1) PostsController#create when logged in should create a new post and
redirect to a successful message page
     Failure/Error: post 'create', { post: {title: 'New post',
       Mock Post(id: integer, title: string, description: text,
location: string, created_at: datetime, updated_at: datetime, status:
string, tags: string, views: integer, user_id: integer) received
unexpected message :id= with (20)
     # ./spec/controllers/posts_controller_spec.rb:56:in `block (4
levels) in <top (required)>'

Finished in 0.59991 seconds
6 examples, 1 failure

I'm trying to figure out this for about a week or more :(

Attachments:
http://www.ruby-forum.com/attachment/7429/posts_controller_spec.rb
http://www.ruby-forum.com/attachment/7430/posts_controller.rb

--

-- 
Posted via http://www.ruby-forum.com/.

How does Spork help in requests specs?

Even with Spork, my requests specs are very slow to start running (about 
7 seconds).

I suspect Rails is booting each time I run "rspec -X spec/requests".

Is that true? If so, is there any way I could instruct the web server to 
keep alive after the specs run so that it would be faster on next run?

Are there any resources on how to have better performance on running 
requests specs with Capybara and Webkit?

Having to wait about 7 seconds between consecutive runs is really a 
blocker for me. If I can't get it to run faster, I'll give up on 
requests specs and only have the controller's tests and client-side code 
specs without any integration tests...

But to be honest, I feel much more comfortable having some integration 
tests for the main features of my application and I would appreciate any 
hints on making them start faster.

The last time I worked with Rails, long ago, it wasn't such a painful 
experience to write such kind of tests (Capybara + Webkit). And my 
current desktop PC is *way* faster than it used to be by that time...

I understand that Rails is much slower to boot now, but maybe there are 
some tricks for reducing the need of rebooting between consecutive 
requests specs run.

Thanks in advance,
Rodrigo.

Bash shim for Rspec

how can I do an "or" within the context of a matcher?

Capybara has two methods:

page.has_button?

and

page.has_link?

...  I am wondering, how can I make a helper method that will be
satisfied by one or the other?  In other words, I want to be able to do:

page.should have_link_or_button("blah")

def have_link_or_button(locator)
  have_link(locator) || have_button(locator)
end

But that doesn't work...  Is there any way to do this?

Patrick J. Collins
http://collinatorstudios.com

overview of how rspec was designed

Stubs and contract tests

how do I test for a status code in a :js => true test?

I have a view with some javascript that does page redirection, and I
wanted to confirm that under certain circumstances the user will get a
500 error from CanCan::AccessDenied.

It seems that when I am not using :js => true, I can do:

page.status_code.shoud be 500

but.. when I try that in a :js => true example group, I get:
Capybara::NotSupportedByDriverError: Capybara::NotSupportedByDriverError

also the request and response objects are nil in the context of this
test...  My dirty workaround has just been to do:

page.has_content "CanCan::AccessDenied"

Which serves my purposes, but I was hoping for a better way...  Any
ideas?

Thank you.

Patrick J. Collins
http://collinatorstudios.com

is there a way to turn on :js => true in the middle of a spec?

Hi,

If I have a spec with some complicated background stuff--  like say for
example logging in...

it "does stuff", :js => true do
  fancy_login_helper_method
  visit somewhere_over_the_rainbow_path
  click_button "omg"
  page.should have_content("waka waka")
end

...  Is there any way to do something like :

it "does stuff" do
  fancy_login_helper_method
  js do
    visit somewhere_over_the_rainbow_path
    click_button "omg"
    page.should have_content("waka waka")
  end
end

So that I can cut down the time it takes to excute that test a bit?  Or
is that just impossible with the way headless vs browser stuff works?

Patrick J. Collins
http://collinatorstudios.com

stub.as_null_object mock and double

Retrying specs

Is it possible to run an example without displaying it's
status ...F...
I'm currently using an around(:each) to run the spec and passing the
example block into vcr however occasionally the cassette needs to be
rerecorded.  I'd like to delay recording it as an error until it has been
retried.  Is that possible currently in rspec?

--

-- 
DryBlis - www.dryblis.com
Samer Masry | Rails Programmer
11 Ambler Ln, Emeryville, CA 94608
Tel.:510-991-7523 | Cel.: 714-814-8508