Hello and happy new year,
David's answer and some digging in RDoc of RSpec has lead to the
following code sceleton:
class Listener
def run_started(number_of_scenarios)
end
def run_ended
end
def story_started(title, description)
end
def story_ended(title, description)
end
On Dec 31, 2007, at 9:22 PM, Chiyuan Zhang wrote:
Hmm, Thanks for your suggestion. I suppose the document of stories
for rspec is not complete yet? Maybe the file layout suggestion could
be included in the document.
ps: Happy New Year to all!
Stories are still a moving target. I was
On Dec 31, 2007, at 1:10 PM, Zach Dennis wrote:
I don't think it is designing less either. It's designing better
and doing it smarter, knowing that you'll never fully comprehend
the domain of your problem upfront, so you discover it,
iteratively. As you discover more about the domain the
On Jan 1, 2008 1:48 PM, Francis Hwang [EMAIL PROTECTED] wrote:
On Dec 31, 2007, at 1:10 PM, Zach Dennis wrote:
I don't think it is designing less either. It's designing better
and doing it smarter, knowing that you'll never fully comprehend
the domain of your problem upfront, so you
I was looking over some of my specs.
I was thinking that the following:
@game.should_receive(:name).and_return('The Battle for Blaze')
@game.should_receive(:people).and_return(500)
@game.should_receive(:activated).and_return(true)
Would it look cleaner if I could do this instead?
