[Seaside] SeasideTesting and WebTester w/ Selenium
joelbywan at gmail.com
Fri Aug 27 04:33:05 UTC 2010
I'm not sure if I'm doing this right.
How do I, with WebTester, test that <div class="foo"> is present? This is
boggling me, and testing something like that seemed pretty obvious with
SeasideTesting. I ended up doing this, but yikes...
self assert: ( self webTester processCommand: 'isElementPresent'
withParams: ( Array with: '//div[@class=''foo'']' )) = 'true'
Am I trying to do something that WebTester is not suited for?
On Wed, Aug 25, 2010 at 8:56 AM, Joel Turnbull <joelbywan at gmail.com> wrote:
> 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.
> On Wed, Aug 25, 2010 at 7:16 AM, C. David Shaffer <cdshaffer at acm.org>wrote:
>> On 08/25/10 06:49, Bart Gauquie wrote:
>> > WebTester opens a browser by sending a http request to Selenium Remote
>> > Control (http://seleniumhq.org/projects/remote-control/). And then
>> > this remote control starts the browser. Selenium Remote Control is a
>> > java process you have to start before starting the selenium tests in
>> > Smalltalk.
>> I see. I'm sure that makes sense for Selenium but for SeasideTesting
>> the best option is raising a browser window from Smalltalk (you could
>> ask the user to do it for you if you are really allergic to FFI). This
>> is especially true on build servers where ST is running inside a VNC
>> session, for example.
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside