Cucumber ".should contain(expected) does but fails anyway

Testing RSpec
21

On Thu, Apr 23, 2009 at 3:16 PM, James B. [email protected]
wrote:

to stick the object_handle method in the right place and get the revised
specs to pass. I should have a patch for you tomorrow. If not, then by
Monday.

Cool. I may need to get a release out before the weekend due to other
pressures, so this might not make it until the next release, but that
won’t be too far off.

Thanks James,
David

22

David C. wrote:

On Thu, Apr 23, 2009 at 3:16 PM, James B. [email protected]
wrote:

to stick the object_handle method in the right place and get the revised
specs to pass. �I should have a patch for you tomorrow. If not, then by
Monday.

Cool. I may need to get a release out before the weekend due to other
pressures, so this might not make it until the next release, but that
won’t be too far off.

Thanks James,
David

NP

23

David C. wrote:

On Thu, Apr 23, 2009 at 2:26 PM, James B. [email protected]
wrote:

David C. wrote:

I’d rather always define our own so the results are consistent from
RSpec regardless of other frameworks in the midst. Does that make
sense to you?

Instead of metaclass how about object_handle ?

wdt?

Go for it. I think that’s good enough for now. It’s for internal
consumption only. Also, I’m better at making naming decisions when I
see things in context, I may change it later if I come up w/ something
that speaks to me more clearly.

Good?

OK. I have made the changes to the code in a local branch. I just need
to stick the object_handle method in the right place and get the revised
specs to pass. I should have a patch for you tomorrow. If not, then by
Monday.

24

David C. wrote:

BTW - FWIW, this is a classic example of how OSS should work. User
gets frustrated. User solves problem through contribution. Thanks for
playing!

Patch is on Lighthouse.

https://rspec.lighthouseapp.com/projects/5645-rspec/tickets/804

I did this on my laptop so some of the file modes are whacked (775 vice
664). It seems that I am not the first to encounter this since I found
other library files in the repository that have mode 775. Nonetheless,
you may wish to tidy this situation up.

25

On Wed, Apr 22, 2009 at 12:18 PM, David C. [email protected]
wrote:

‘==’)
    expected "Bank of Canada: Noon Foreign Exchange

WDYT?

I like the idea, though I think it’s helpful to also have the strings
in the case of String objects. But having the class and object id
would really help tell the story we’re looking for.

wdYt?

I like this idea. Maybe you show the object id and a truncated string.
i.e.

expected “#String:0x2b6950315300 (Four score and seven years…)”
got “#String:0x2b695026e898 (Four score and seven
years…)”
using equal?

So it’s clear that they’re different objects, and you get a bit of
context to figure out which string it’s referring to.

Pat

26

On Thu, Apr 23, 2009 at 3:17 PM, David C. [email protected]
wrote:

Instead of metaclass how about object_handle ?
OK. I have made the changes to the code in a local branch. I just need
to stick the object_handle method in the right place and get the revised
specs to pass. I should have a patch for you tomorrow. If not, then by
Monday.

Cool. I may need to get a release out before the weekend due to other
pressures, so this might not make it until the next release, but that
won’t be too far off.

BTW - FWIW, this is a classic example of how OSS should work. User
gets frustrated. User solves problem through contribution. Thanks for
playing!

27

James B. wrote:

Patch is on Lighthouse.

Lighthouse - Beautifully Simple Issue Tracking

Besides Fixnum, are there any other Ruby Class Objects that do not have
a virtual class?