Very helpful, thank you. It occurred to me last night as I was playing some more with WebTester that it isn't necessarily a mutually exclusive decision. Like Johan stated, each can be utilized for different kinds of testing.<br>
<br><br><div class="gmail_quote">On Wed, Aug 25, 2010 at 7:16 AM, C. David Shaffer <span dir="ltr"><<a href="mailto:cdshaffer@acm.org">cdshaffer@acm.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"> On 08/25/10 06:49, Bart Gauquie wrote:<br>
> WebTester opens a browser by sending a http request to Selenium Remote<br>
> Control (<a href="http://seleniumhq.org/projects/remote-control/" target="_blank">http://seleniumhq.org/projects/remote-control/</a>). And then<br>
> this remote control starts the browser. Selenium Remote Control is a<br>
> java process you have to start before starting the selenium tests in<br>
> Smalltalk.<br>
><br>
<br>
</div>I see. I'm sure that makes sense for Selenium but for SeasideTesting<br>
the best option is raising a browser window from Smalltalk (you could<br>
ask the user to do it for you if you are really allergic to FFI). This<br>
is especially true on build servers where ST is running inside a VNC<br>
session, for example.<br>
<div><div></div><div class="h5"><br>
David<br>
<br>
_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
</div></div></blockquote></div><br>