[Pharo-dev] TestCase Announcers classvar is bizarre

Stéphane Ducasse stephane.ducasse at inria.fr
Fri Aug 30 16:35:14 EDT 2013


> 
> 
> i didn't said i don't believe it.
> But what someone said (it was Esteban or someone else) in conversation,
> that existence of documentation does not guarantees there will be no abuses. 
> Because , at the end, the developer can simply disagree with author's POV,
> and so he intentionally picks "not recommended" way.
> Of course it is not an excuse for not writing a documentation :) 

:)

Igor if you write some notex in telegraphic styles I can spend time fleshing them .


> 
> stef
> 
> On Aug 30, 2013, at 1:45 PM, Igor Stasenko <siguctua at gmail.com> wrote:
> 
>> 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.
> 
> 
> 
> 
> -- 
> Best regards,
> Igor Stasenko.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20130830/1ac7b1c6/attachment-0002.html>


More information about the Pharo-dev mailing list