[Pharo-dev] [Seaside] [ANN] SeasideTesting recovered from oblivion

Norbert Hartl norbert at hartl.name
Tue Oct 24 02:50:03 EDT 2017

Cool. Need to think where it is useful. On the one hand testing without external components is good. On the other hand you can only test very simple stuff with it. But there might be a place.
Btw. you don‘t need selenium with parasol. You can use chrome-standalone which implements the same protocol.


> Am 23.10.2017 um 12:04 schrieb Esteban Lorenzano <estebanlm at gmail.com>:
> 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/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,
> cheers!
> Esteban
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20171024/c9a0feac/attachment-0002.html>

More information about the Pharo-dev mailing list