Hello, Thanks. Very nice library!
I have a question: is it possible to expect a method to throw an Exception? I would like something like: protocol describe once: mock recv: #aMethod ; signal: anError. I did not find anything in the documentation. I don't want to test that the mock signals an error but I want to test a code that needs to take into account an exception. Best regards, Christophe. Le 11 mars 2014 à 12:30, Attila Magyar a écrit : > I'm pleased to announce the 2.0 version of BabyMock. BabyMock is a visual > mock object library that supports test-driven development. > > This version has a new syntax which is incompatible with the old version. > Therefore it has a new repository > http://smalltalkhub.com/#!/~zeroflag/BabyMock2 > (BabyMock 1 is still available at its old location, but in the future I'd to > focus on the development of BabyMock2, so don't expect too many changes > regarding the old version). > > Changes in 2.0 > > - A new, extensible DSL (no more should/can) > - Improved error messages, history of messages, detailed information about > argument mismatches > - An improved, Spec based GUI > - Clicking on a mock opens an inspector on the expectations > - Clicking on a message opens an inspector on the message > - Object methods can be mocked by defaults > - Blocks can be executed after receiving a message by the mock. The block > has access to the arguments of the incoming message. > - Any argument matcher > - Cleanups and simplifications in the code > > I hope you don't mind the changes regarding the syntax. Personally I think > it has lot more pros than cons. > > More information > > http://smalltalkhub.com/#!/~zeroflag/BabyMock2 > > p.s. > It needs Pharo3.0. > > Attila > > > > -- > View this message in context: > http://forum.world.st/ANN-BabyMock-2-tp4748530.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >
smime.p7s
Description: S/MIME cryptographic signature