FYI, we are already using Phexample in Moose since several years, and it just works out of the box next to Sunit.

Doru

On Wednesday, January 23, 2013, Sven Van Caekenberghe wrote:
Yes we #should ;-)

It is beautiful.

On 23 Jan 2013, at 11:04, Camillo Bruni <camillobruni@gmail.com> wrote:

> check the project page for all examples and explanations:
>
> http://smalltalkthoughts.blogspot.ch/2009/11/phexample-because-examples-expand-on.html
> http://www.iam.unibe.ch/~akuhn/blog/2009/shoulda-use-this-in-pharo
>
> to me this feels more like Smalltalk and less like Java ;)
>
> On 2013-01-23, at 08:47, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> wrote:
>> Who should assert then?
>> From a certain POV, it does not seem that awfully unlogical to
>> delegate this responsability to a TestCase.
>> A TestCase is here to assert some rule.
>>
>> Nicolas
>>
>> 2013/1/23 Camillo Bruni <camillobruni@gmail.com>:
>>> for that we already have a fully working Phexample:
>>>
>>> http://www.squeaksource.com/phexample.html
>>>
>>> which I will push in 3.0, cause I never really liked #assert: and friends being
>>> sent to self. Furthermore we could finally build up decent messages!
>>>
>>> On 2013-01-22, at 18:24, St�phane Ducasse <stephane.ducasse@inria.fr> wrote:
>>>
>>>> it would be nice to introduce the same syntax than Sunit
>>>>
>>>> � � exp assert: exp2
>>>>
>>>> � � [ exp ] shouldraise:
>>>>
>>>> Stef
>>>>
>>>>
>>>> On Jan 21, 2013, at 4:41 AM, Benjamin wrote:
>>>>
>>>>> Hi guys,
>>>>>
>>>>> I am attending a python lecture and discovered DocTest[1], and I was wondering if such a tool exists for Pharo ? :)
>>>>>
>>>>>
>>>>> Ben
>>>>>
>>>>> [1]http://docs.python.org/2/library/doctest.html
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>
>




--
www.tudorgirba.com

"Every thing has its own flow"