TestCase Announcers classvar is bizarre
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 ... and.. do we need so many announcers everywhere? -- Best regards, Igor Stasenko.
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. 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...
... and.. do we need so many announcers everywhere?
-- Best regards, Igor Stasenko.
On 30 August 2013 13:31, Camille Teruel <camille.teruel@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.
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@gmail.com> wrote:
On 30 August 2013 13:31, Camille Teruel <camille.teruel@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.
you still do not believe me but I really think that wirting some documents on what are the practices what ae the good practices and what are the bad practices is important just to make sure that people can refer to it in case. stef On Aug 30, 2013, at 1:45 PM, Igor Stasenko <siguctua@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@gmail.com> wrote:
On 30 August 2013 13:31, Camille Teruel <camille.teruel@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.
On 30 August 2013 13:52, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
you still do not believe me but I really think that wirting some documents on what are the practices what ae the good practices and what are the bad practices is important just to make sure that people can refer to it in case.
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 :) stef
On Aug 30, 2013, at 1:45 PM, Igor Stasenko <siguctua@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@gmail.com> wrote:
On 30 August 2013 13:31, Camille Teruel <camille.teruel@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.
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@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@gmail.com> wrote:
On 30 August 2013 13:31, Camille Teruel <camille.teruel@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.
On 30 août 2013, at 13:38, Igor Stasenko wrote:
On 30 August 2013 13:31, Camille Teruel <camille.teruel@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?
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.
participants (4)
-
btc＠openinworld.com -
Camille Teruel -
Igor Stasenko -
Stéphane Ducasse