[Pharo-dev] TestCase Announcers classvar is bizarre

Igor Stasenko siguctua at gmail.com
Fri Aug 30 07:45:27 EDT 2013


the more i looking how people using announcements, the more it reminds me
the quote:
if the only *tool* you have is a *hammer*, to treat everything as if it
were a *nail*


On 30 August 2013 13:38, Igor Stasenko <siguctua at gmail.com> wrote:

>
>
>
> On 30 August 2013 13:31, Camille Teruel <camille.teruel at gmail.com> 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?
>
>
>> 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??
>
>
>
>> > ... and.. do we need so many announcers
>> > everywhere?
>> >
>> > --
>> > Best regards,
>> > Igor Stasenko.
>>
>>
>>
>
>
> --
> Best regards,
> Igor Stasenko.
>



-- 
Best regards,
Igor Stasenko.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20130830/09cfbbd3/attachment-0002.html>


More information about the Pharo-dev mailing list