- Other features: I don’t use most of the fancy features, but I do find
stubs useful. Do you expect people to use when_told_to without
was_told_to? in order to stub something out?
- I also find the ‘null object’ pattern useful. That is where the
isolated object always returns nil to methods called on it.
- Finally, I’ve been slow on pushing lately because I’m moving, I’ll do
a push when I get to decent internet. I’ll also work on automating thid
in the next couple of weeks.
…there is no try
Sent from my phone. Please excuse typos and txtspk.
1: Yes stubbed by default and only when you’re actually interested in
asserting if it was called you use the was_told_to? assertion2: Yes
null unless you explicitly tell it to fall through to the implementation
the method. I may make use of the default(T) thing later on to return
default value for value types.
3: no problem I was just curious about that
Met vriendelijke groeten - Best regards - Salutations
Ivan Porto C.
Author of IronRuby in Action (http://manning.com/carrero)
- “If voting changed anything, they’d make it illegal.”
I- tried the pure stubbing approach as did Pete Y. with his
rails plugin - the stubs will return nil for any method call unless to
them to do otherwise (return something, yield something and/or raise
something). So everything is a stub (just one that happens to be a .net
interface implementation) that records all calls for later inspection.
The null object i’ll add next (the stubs will just return another stub
instead of nil and record all calls).
The assertions are then at the end of the test/spec (where I think all
expectations should be) - at this stage you need to scan the list of
recorded calls - i’ll add some syntax to do nicer checking.
Does your final point suggest that the event implementation will be