[Bug] TestCase>>shouldnt:triggerAnyOf:against:

I noticed that the TestCase method #shouldnt:triggerAnyOf:against: looks
to have the same problem with using getEvents/setEvents: that
#should:triggerAllOf:matching:butNoneOf:against: used to have. I think
that it should just be implemented in terms of the underlying workhorse
method:


        !TestCase methodsFor!

        shouldnt: aBlock triggerAnyOf: aCollectionOfSymbols against: anObject
                self
                        should: aBlock
                        triggerAllOf: #()
                        matching: [:message | true]
                        butNoneOf: aCollectionOfSymbols
                        against: anObject! !

-------------------------------------------
Bill Dargel            [hidden email]
Shoshana Technologies
100 West Joy Road, Ann Arbor, MI 48105  USA

"Bill Dargel" <[hidden email]> wrote in message
news:[hidden email]...
> I noticed that the TestCase method #shouldnt:triggerAnyOf:against: looks
> to have the same problem with using getEvents/setEvents: that
> #should:triggerAllOf:matching:butNoneOf:against: used to have. I think
> that it should just be implemented in terms of the underlying workhorse
> method:
>
> [ method snipped ]

Yes, sorry that appears to have been overlooked when the patch for #1158 was
created by copying a method from D6. In fact the implementation I have for
#shouldnt:triggerAnyOf:against: in my D6 development image is exactly that
you suggest.

Regards

Blair