Hello guys, a feature idea/request⦠This weekend I was binge-watching talks from Ruby conferences, by Sandi Metz and Katrina Owen on OO design, refactoring, and testing. Highly recommended, and at least Sandi is an experienced smalltalker. See for instance RailsConf 2016 - Succession by Katrina Owen <https://www.youtube.com/watch?v=59YClXmkCVM> or Rails Conf 2013 The Magic Tricks of Testing by Sandi Metz <https://www.youtube.com/watch?v=URSWYvyc42M> In particular, in the second one, Sandi remarks that there is a risk that the application API diverges from the set of messages checked with the mocks. There are tools to help with that, mostly involving the mocks checking that each message they expect actually exists in the application. In Mocketry, mocks are created ex-nihilo, but it could be nice to pass a reference class to compare with, or for the mock to check that there are implementors of the message. On 20 April 2016 at 22:54, Tudor Girba <tudor@tudorgirba.com> wrote:
Thank you!
Doru
On Apr 20, 2016, at 10:35 AM, Denis Kudriashov <dionisiydk@gmail.com> wrote:
2016-04-20 2:27 GMT+02:00 Sean P. DeNigris <sean@clipperadams.com>: Tudor Girba-2 wrote
It is your prerogative :), but âshould got" sounds broken :(.
Sounds like fingernails on a chalkboard IMH-native-english-speaker-O ;)
Ok. I open new thread about names
-- www.tudorgirba.com www.feenk.com
"It's not how it is, it is how we see it."
-- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet