On Oct 25, 2010, at 10:12 AM, Niko Schwarz wrote:
> Couldn't Adrian be the maintainer? I could step in, too.
yes but it means being present and reactive.
> I don't really know what you have in mind for a testing framework. We
> have our own independent and fully compatible fork of SUnit:
> akuhn/SUnit, which is quite a strong code basis.
but do we need should, class factory.....
> And on top of that we
> have Phexample, which has its own
> name, some extra features and gives a clear point where Pharo is
> different from the rest.
This is not the difference that we look for. This is addressing people problems.
> Just a suggestion: Let Adrian maintain akuhn/SUnit, perhaps minus the
> "should" syntax that you don't like (as in: #(a b c) size should = 3),
> and make akuhn/SUnit part of Pharo core. The new features (having tests depend
> on one another, "should" syntax) go into Phexample, and I could
> maintain that.
Why not. If adrian wants.
Now first we should have
- a better name
- clean the code = remove class factory + add comments
- make sure that the tools can work with it
- move the long execution Sunit extension to it
- make sure that the tests are green
- integrate/digest latest Sunit feature
>
> Cheers,
>
> Niko
>
> On Sun, Oct 24, 2010 at 8:37 AM, Stéphane Ducasse
> <[email protected]> wrote:
>> Lack of maintainers, too many unwanted features, lack of explanation,
>> large changes...
>>
>> And this is not that several persons did not look at the code. It got more
>> than the average.
>>
>> Now I'm thinking that with discussion and care we should really get another
>> testing framework with the same API that SUnit
>> because if we want that PharoSunit is the same as Sunit then we are doomed
>> to be backward compatible and no
>> real improvements.
>>
>> Stef
>>
>> On Oct 23, 2010, at 10:58 PM, Adrian Kuhn wrote:
>>
>>> Sad to hear that.
>>>
>>> Technical difficulties, or just lack of customers? ^^
>>>
>>> --AA
>>>
>>> On Oct 23, 2010, at 08:05 , Stéphane Ducasse wrote:
>>>
>>>> It was too difficult to integrate.
>>>>
>>>> Stef
>>>>
>>>> On Oct 23, 2010, at 2:01 PM, Niko Schwarz wrote:
>>>>
>>>>> What's the status of akuhn/SUnit? I couldn't find his code in 1.2 core.
>>>>>
>>>>> Niko
>>>>>
>>>>> On Wed, Feb 3, 2010 at 1:13 PM, Stéphane Ducasse
>>>>> <[email protected]> wrote:
>>>>>> this loads well in the latest 1,1 core :)
>>>>>> so now we should really have a look and these cool changes
>>>>>>
>>>>>> Stef
>>>>>>
>>>>>> On Jan 6, 2010, at 2:38 PM, Adrian Kuhn wrote:
>>>>>>
>>>>>>> SystemChangeNotifier uniqueInstance
>>>>>>> noMoreNotificationsFor: TestCase.
>>>>>>> Gofer it
>>>>>>> disablePackageCache;
>>>>>>> squeaksource: 'akuhn';
>>>>>>> package: 'SUnit';
>>>>>>> package: 'SUnitGUI';
>>>>>>> load.
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Pharo-project mailing list
>>>>>> [email protected]
>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> http://scg.unibe.ch/staff/Schwarz
>>>>> twitter.com/nes1983
>>>>> Tel: +41 076 235 8683
>>>>>
>>>>> _______________________________________________
>>>>> Pharo-project mailing list
>>>>> [email protected]
>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>>
>>>
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [email protected]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
>
>
> --
> http://scg.unibe.ch/staff/Schwarz
> twitter.com/nes1983
> Tel: +41 076 235 8683
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
