On Nov 18, 2008, at 8:46 AM, Einar Magn=FAs 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 =20=

> you expect tests to fail at first, maybe this is different in BDD =20
> than in TDD, I don't know enough about BDD. Especially when you use =20=

> tests to design interfaces the "should" thinking comes more natural: =20=

> You don't have a feature yet but you write down what it should do, =20
> then you implement it.

Announcing yet another test framework: Musty!

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

the right thing already, right?

-Tobias=