Re: [Pharo-users] Why is the root class of tests named TestAsserter?

[Alidra Abdelghani via Pharo-users]

--- Begin Message ---

Hi James,

Thanks a lot for this very interesting historical perspective :)
Still I think TestAsserter is not the most intuitive name. Asserter is not even 
an English word if I am not mistaken.

Thanks again
Abdelghani

> On 10 Oct 2018, at 1:57 pm, James Foster <smallt...@jgfoster.net> wrote:
> 
> Hi Abdelghani,
> 
> I don’t have immediate access to earlier versions of SUnit (oh, that it were 
> on GitHub!), but my recollection is that TestCase was originally a root class 
> but duplicate code with TestResource inspired a refactoring that called for a 
> common superclass. The name TestAsserter was chosen to reflect the common 
> behavior.
> 
> James
> 
>> On Oct 9, 2018, at 8:12 AM, Alidra Abdelghani via Pharo-users 
>> <pharo-users@lists.pharo.org <mailto:pharo-users@lists.pharo.org>> wrote:
>> 
>> 
>> From: Alidra Abdelghani <alidran...@yahoo.fr <mailto:alidran...@yahoo.fr>>
>> Subject: Why is the root class of tests named TestAsserter?
>> Date: October 9, 2018 at 8:12:11 AM PDT
>> To: pharo-users@lists.pharo.org <mailto:pharo-users@lists.pharo.org>
>> 
>> 
>> Hi,
>> 
>> I am trying to understand how classes in smalltalk projects are named. 
>> Something I can hardly understand is why the root class of the Test 
>> hierarchy is named TestAsserter?
>> What is the intention behind the term Asserter?
>> Wouldn’t it be more appropriate to name it AbstractTest since most classes 
>> of this hierarchy are Tests?
>> 
>> Many thanks in advance
>> Abdelghani
>> 
>> 
>> 
> 

Dr. Abdelghani Alidra 
Enseignant-chercheur
Université 20 août 1955
SKIKDA-ALGÉRIE 
Mob:+ 213 550 453 391

--- End Message ---