[Pharo-project] Phexample integrated with Autotest and OB (was ConfigurationOfPhexample (was #assert:equals: feels backwards))

laurent laffont laurent.laffont at gmail.com
Fri Jun 24 18:00:52 EDT 2011


On Fri, Jun 24, 2011 at 9:39 PM, Sean P. DeNigris <sean at clipperadams.com>wrote:

>
> laurent laffont wrote:
> >
> > I suppose you have patched TestCase class>>allTestSelectors  so it can
> > find
> > shouldXXX methods ?
> >
>
> Nope, although anyone wanting #shouldXxx methods in TestCase could do that.
> Phexample overrides #allTestSelectors to return both testXxx and shouldXxx
> and does the work for us.
>
> Using #allTestSelectors leaves the decision up to the library (so if people
> start wanting testThatItShouldXxx or whatever, it'll still work). The other
> advantage is that the behavior of OB, Autotest, and other testing tools
> will
> stay in sync with the behavior of the underlying SUnit system.
>
>
OK. I've updated ConfigurationOfAutotest.


laurent laffont wrote:
> >
> > AutotestTestFinder>>testMethodsForMethodThatStartWithShouldReturnsIt
> >
> I think this behavior is now under the SUnit umbrella and doesn't have to
> be
> tested, no?
>

Agree.

Laurent



> Sean
>
> --
> View this message in context:
> http://forum.world.st/Phexample-integrated-with-Autotest-and-OB-was-ConfigurationOfPhexample-was-assert-equals-feels-backw-tp3623325p3623440.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20110625/0219fad5/attachment-0001.html>


More information about the Pharo-dev mailing list