[Seaside] SeasideTesting and WebTester w/ Selenium
johan at inceptive.be
Wed Aug 25 06:22:00 UTC 2010
Did you install SeasideTesting using the Metacello configuration? Or did you load the SeasideTestingR29 package? This last one is the old version. I now recommend using the new version.
The SeasideTesting package for Pharo/Squeak is a 'port in progress' (this is work from David Shaffer who is now developing in VW). The simulated browser testing should work but the testing using the external browser (which will let you use the jQuery examples you refer to) has not been ported yet.
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.
On 24 Aug 2010, at 20:15, Joel Turnbull wrote:
> I'm a little confused about the state of the SeasideTesting package.
> I started with this tutorial http://bit.ly/aEwrSb. Installing the latest package in Pharo, it was obvious that I either had the wrong package, or things had changed quite a bit since that was written. But, using a combination of that tutorial, and the example classes, I've been able to successfully use it, and like it, until I got into my components that utilize jQuery. I see in the tutorial that there are some methods like assertEventually: that were provided to handle jQuery calls. However quickly browsing through the classes in my SeasideTesting package, I seem to be missing jQuery examples, or methods that compare to assertEventually:
> So last night I took a look at Selenium RC and WebTester, and was pretty impressed ( http://bit.ly/cr2vjK ). Seems like it can definitely handle my jQuery problem.
> However before I consider switching, I wanted to get the opinions and recommendations of those on the list regarding these two options, as I've already done quite a bit of work in SeasideTesting, and I'm pretty sure that I'm just missing how to use it with jQuery. Also, do you foresee any problems with either of these testing frameworks if I need to scale up to Gemstone?
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside