On Nov 18, 2008, at 8:46 AM, Einar Magnů¸ Boson wrote:

> But you are setting up an expectation, right?
>
> my_method.must.do_the_right_thing.
> it didn't? but it must!
>
> my_method.should.do_the_right_thing.
> it didn't, but it should!
>
> For me the second example feels more natural in a environment where  ou expect tests to fail at first, maybe this is different in BDD  
> than in TDD, I don't know enough about BDD. Especially when you use  ests to design interfaces the "should" thinking comes more natural:  ou don't have a feature yet but you write down what it should do,  
> then you implement it.

Announcing yet another test framework: Musty!

Its perfect for dusting off that old, untested code and bringing it  
into the modern era! Since its already in production, it MUST be doing  he right thing already, right?