[Seaside-dev] self shouldnt: [ whatever ] raise: Error.
Johan Brichau
johan at inceptive.be
Sun Oct 20 14:17:07 UTC 2013
Indeed.
In the case of the now failing tests in Seaside, it is actually meaningful to test if no error is thrown. The assertion is a documentation what is being tested.
At first thought, I had the idea that it was easy to remove the assertion since the test will fail if an error is thrown anyway. However, without the assertion, the meaning of the test now has to be written in comments.
The spirit behind the idea seems good, but enforcing it like this is counter-productive in some cases.
Johan
On 20 Oct 2013, at 15:53, Philippe Marschall <philippe.marschall at gmail.com> wrote:
> On Sun, Oct 20, 2013 at 3:40 PM, Jan van de Sandt <jvdsandt at gmail.com> wrote:
>> It was also posted on the Pharo-dev mailing list:
>> http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2013-September/084101.html
>
> I don't even know where to begin.
>
> Cheers
> Philippe
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
More information about the seaside-dev
mailing list