[Pharo-dev] [Seaside] [ANN] SeasideTesting recovered from oblivion
johan at inceptive.be
Mon Oct 23 18:24:26 EDT 2017
I think we prefer a slower but accurate testing proces, using Parasol.
> On 23 Oct 2017, at 22:22, Jon Paynter <kittle31 at gmail.com> wrote:
> Great to hear!
> I use this on some older projects, and found the documentation helpful, but also sketchy. Hopefully you can update things.
> Will your resurected version work with Visualworks?
>> On Mon, Oct 23, 2017 at 3:04 AM, Esteban Lorenzano <estebanlm at gmail.com> wrote:
>> I spend some days last week woking with the guys of AFI (http://afi-sa.fr, yes they also use Pharo in some of their projects) and together we recovered SeasideTesting from Davis Shaffer to be used for their TDD experience.
>> you can check it out here: https://github.com/Afibre/SeasideTesting
>> What’s SeasideTesting? A package to test Seaside components.
>> Why we do not use Parasol? Because it is based on selenium and that makes the process slow.
>> Where can I know more?
>> - there is some documentation here (for VW, I think): http://www.shaffer-consulting.com/david/Seaside/TestingComponents/TestingComponents.html
>> - some slides here (on squeak): http://esug.org/data/ESUG2005/Wednesday/2005-ESUG-Shaffer.pdf
>> but all that is old. Best way is to just install and see the tests, as always,
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pharo-dev