Re: [Pharo-users] The confusing state of SUnit

2019-02-27 Thread Tim Mackinnon
No - my point is, why are the basics for reasonable testing not in the image? Such that tests are easy, and a joy to write where failures are obvious when they occur. We seem to have 2 extremes - assert:equals: does a lovely job of showing what it expects and you got with a nice diff view (that

Re: [Pharo-users] The confusing state of SUnit

2019-02-26 Thread jtuc...@objektfabrik.de
So you are suggesting an extension of SUnit. Great. You just forgot to attach your code ;-) BTW: I think the current imnplementations of SUnit already carry a large amount of pollution. Just because JUnit and friends introduced special methods for testing equality and such, we also have this n

Re: [Pharo-users] The confusing state of SUnit

2019-02-26 Thread Gabriel Cotelli
We have some extensions in Buoy just for that. https://github.com/ba-st/Buoy/blob/release-candidate/docs/SUnit.md On Tue, Feb 26, 2019, 21:15 Tim Mackinnon wrote: > Forgive me father, for I have sinned… but when I try to right good tests, > that fail in a way I can understand them it seems that

[Pharo-users] The confusing state of SUnit

2019-02-26 Thread Tim Mackinnon
Forgive me father, for I have sinned… but when I try to right good tests, that fail in a way I can understand them it seems that SUnit doesn’t want to help me… Maybe I am missing something, but in 2019 it should be easy to write tests - particularly when we want people to contribute to adding mo