I don’t know... we maintained SeasideTesting at http://smalltalkhub.com/#!/~Seaside/SeasideTesting/ until we developed Parasol because it just covers some bare-bones html page testing. Forget about JavaScript and css influence on your tests in seaside testing. I think we prefer a slower but accurate testing proces, using Parasol. Johan

On 23 Oct 2017, at 22:22, Jon Paynter <kittle31@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@gmail.com> wrote: Hi,

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/TestingCom... - 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,

cheers! Esteban

_______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside