On 21 Apr 2015, at 10:36, Christophe Demarey <Christophe.Demarey@inria.fr> wrote:

To come back to my proposition, it is just a first step to BDD to not prevent people to define tests with something like shouldAccountBalanceBePositiveAfterEachOperation (more behavior driven) rather than testMyWonderfulMethod that may leads people to test the implementation details and not the expected behavior.

Not that your naming ideas are bad, but right now you can write

testAccountShouldBePositiveAfterEachOperation

which is not that bad

• SUnit
• BabyMock (http://smalltalkhub.com/#!/~zeroflag/BabyMock2)
• Mocketry (http://smalltalkhub.com/#!/~dionisiy/Mocketry)
• PhExample (http://smalltalkhub.com/#!/~PharoExtras/Phexample)
• BoTest (http://smalltalkhub.com/#!/~CAR/BoTest)
• Kiwi TDD (https://www.youtube.com/watch?v=m2t_MbVAdis)
• and maybe others.