April 5, 2012
10:14 a.m.
Hello guys, I was implementing in Nautilus a listener to TestCaseStarted, and then I figured out that each TestCase subclasses have its own Announcer. It means that you have to know which class to register to instead of which announcer. In a way, it breaks the Observer pattern. Is there any good reason I am missing ? I think it has been done in a way you can spy a particular test class, but since you have this info in the announcement itself, you can always filter with this info. Cause for me, replacing all those announcer by TestAnnouncer seems to be a better solution. Thanks in advance, Ben