[Seaside] SeasideTesting and WebTester w/ Selenium

C. David Shaffer cdshaffer at acm.org
Wed Aug 25 10:33:54 UTC 2010

 On 08/25/10 02:22, Johan Brichau wrote:
> I am currently also using both SeasideTesting and WebTester for testing our Seaside application. The first one for 'raw' component testing and the second one for in-browser behaviour testing. 
> Given that SeasideTesting will rely on FFI for external browser testing and that WebTester uses sockets for that, my impression is that WebTester will have no problem to get to work in Gemstone. I am therefore pondering on how to proceed with the port of the external browser testing in SeasideTesting. I have the impression it makes more sense to combine SeasideTesting and WebTester for this.

SeasideTesting only needs a way to raise the browser on a URL.  After
that, all communication is done via HTTP.  So FFI is needed, but only if
that's how you open an external web browser from Squeak/Pharo.  How does
WebTester open the initial web browser window...if it doesn't need FFI
then I suggest using the same mechanism with the SeasideTesting port.


More information about the seaside mailing list