On 30 août 2013, at 13:38, Igor Stasenko wrote: > > > > On 30 August 2013 13:31, Camille Teruel <[email protected]> wrote: > > On 30 août 2013, at 13:16, Igor Stasenko wrote: > > > can someone explain me, PLEASE, what is it for, > > and why there are announcer per each subclass of TestCase needed > > and why you organize it in a dictionary > > It should be a class side instance variable instead of a classVar that maps > test cases to announcer. > > why?
Just because if one wants one <whatever> per class, using a class-side inst var seems better than a class-<whatever> dictionary class var. But as you said, SUnit could use only one announcer anyway. > Anyway the whole announcement stuff in SUnit is weird. > There TestAnnouncement (used by TestRunner) and an independent > TestCaseAnnouncement hierarchy (that nobody use). > And there is this TestAnnouncer that subclass SystemAnnouncer... > > that i already dealt with. > > But really.. why whole SUnit package needs more than one announcer announcing > all events happening about running tests, > why people so obsessive with announcers that they put them everywhere?? Don't know, do a survey ;) > > > ... and.. do we need so many announcers > > everywhere? > > > > -- > > Best regards, > > Igor Stasenko. > > > > > > -- > Best regards, > Igor Stasenko.
