With respect to Seaside (and its cross-platform-ness), this is probably a good decision, for now.
But it is fundamentally unfair to call this an arbitrary unimportant change meant to annoy people. On the contrary ! I even think that there are too many methods in TAssertable and the #shouldnt: checks are very confusing and are candidates for removal, IMHO. Too much unnecessary code is not good in the long run.
Have you ever written a #shouldnt: test ? I have never done so !
I took a Seaside image and looked at the senders of #shouldnt: and friends. There are that many from Seaside and I havenât seen any good example that could not be written otherwise.
My 2c.
They are important :) Would be good to make a pass on TAssertable too. I will add a discussion and a big warning in the SUnit Chapter for the next release of the PBE. Because Camillo is right. shouldnt:raise: Error should not be used. Stef