[Nitro] Web App Testing with Selenium

Aidan Rogers aidan at yoyo.org
Wed Apr 12 19:48:40 EDT 2006

Well, let's say you record a test using the proxy.  Then you make  
some changes to the JavaScript on the client side.  All of a sudden,  
one of your input boxes doesn't display any more, or you've  
accidentally turned a text field into a hidden field.  The proxy  
recording will still work, because it tests the server's reaction to  
specific inputs.  The client side will be broken.

Selenium removes that concern.  Of course, it has problems of its own  
(browser compatibility, poor support for frames, etc.)

Proxy browse/record has been around for a long time, and it has it's  
spot in testing, but generally it's way better for performance  
testing than for functional tests.


On 13/04/2006, at 1:07 AM, George Moschovitis wrote:

>> The big issue with record/playback testing in a proxy fashion is  
>> that you
>> don't test anything client-side.
> what do you mean? For example you can make the same test as
> demonstrated in the video, ie assert for specific tests, test for
> exception, assert time to render etc...

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20060412/746398ae/attachment.html 

More information about the Nitro-general mailing list