Comments on: Selenium rocks - and you don’t need it http://www.magpiebrain.com/blog/2007/01/28/selenium-rocks-and-you-dont-need-it/ Sam Newman's blog Fri, 21 Nov 2008 17:47:19 +0000 http://wordpress.org/?v=2.6.3 By: Ahmed Ashour http://www.magpiebrain.com/blog/2007/01/28/selenium-rocks-and-you-dont-need-it/#comment-151188 Ahmed Ashour Sat, 11 Oct 2008 15:25:07 +0000 http://www.magpiebrain.com/blog/2007/01/28/selenium-rocks-and-you-dont-need-it/#comment-151188 http://htmlunit.sf.net is another powerful java browser emulator http://htmlunit.sf.net is another powerful java browser emulator

]]> By: sam http://www.magpiebrain.com/blog/2007/01/28/selenium-rocks-and-you-dont-need-it/#comment-12411 sam Tue, 27 Feb 2007 08:45:55 +0000 http://www.magpiebrain.com/blog/2007/01/28/selenium-rocks-and-you-dont-need-it/#comment-12411 Which was the point of the article - anything (not just Javascript) which manipulates the DOM after the page has been served will require in-browser testing - either manual or automated. But understand when you make that choice (even Javascript heavy apps will serve some static data). One approach to making Javascript-heavy apps testable using static, outside-browsr verification is to decompose the content of each page into a series of components, each one available on it's own URL. Which was the point of the article - anything (not just Javascript) which manipulates the DOM after the page has been served will require in-browser testing - either manual or automated. But understand when you make that choice (even Javascript heavy apps will serve some static data).

One approach to making Javascript-heavy apps testable using static, outside-browsr verification is to decompose the content of each page into a series of components, each one available on it’s own URL.

]]> By: Anonymous http://www.magpiebrain.com/blog/2007/01/28/selenium-rocks-and-you-dont-need-it/#comment-12385 Anonymous Tue, 27 Feb 2007 04:18:22 +0000 http://www.magpiebrain.com/blog/2007/01/28/selenium-rocks-and-you-dont-need-it/#comment-12385 Selenium comes in very handy when your application makes heavy use of Javascript. For example, HtmlUnit currently chokes on trying to parse the standard Dojo include files, so any application which uses Dojo isn't testable by HtmlUnit. Selenium, since it uses the actual browser, doesn't have this problem. So for my team at least, it's Selenium or nothing... Selenium comes in very handy when your application makes heavy use of Javascript. For example, HtmlUnit currently chokes on trying to parse the standard Dojo include files, so any application which uses Dojo isn’t testable by HtmlUnit. Selenium, since it uses the actual browser, doesn’t have this problem. So for my team at least, it’s Selenium or nothing…

]]>