#424 √ invalid
Kevin Ballard

Object#should_not_receive does not accept :expected_from

Reported by Kevin Ballard | May 30th, 2008 @ 06:41 AM | in No-Milestone-Assigned

Object#should_receive can take options, specifically :expected_from, but Object#should_not_receive does not have this same ability.

Comments and changes to this ticket

  • Pat Maddox

    Pat Maddox August 11th, 2008 @ 10:20 PM

    • → Tag changed from “” to “bug mocks”

    I don't know that it makes sense for #should_not_receive to take :expected_from. What would that mean? That the target object is allowed to receive the method call, as long as it's not from a particular file and line number?

  • Kevin Ballard

    Kevin Ballard August 11th, 2008 @ 10:43 PM

    I don't remember anymore what I wanted this for, or even how I expected it to act. I had some desired behavior in mind, I just can't recall now what it was.

  • Pat Maddox

    Pat Maddox October 21st, 2008 @ 12:29 AM

    • → State changed from “new” to “invalid”

    Closing this for the time being. It doesn't make any sense to me, but I'm willing to revisit if someone really wants it later

Please Login or create a free account to add a new comment.

You can update this ticket by sending an email to from your email client. (help)

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Behaviour Driven Development for Ruby.

Shared Ticket Bins

People watching this ticket

Tags