Personally, I hit the wall wilth HTMLUnit and had to move to Selenium RC. The problem was that HTMLUnit had problems as soon as I upgraded from Tapestry 4 to Tapestry 4.1 due to the inclusion of Dojo libraries. I assume these will be fixed eventually, but I am much happier having my tests run in the actual browser (even on a headless linux box!) and it really helps to see what is going when stepping through in the debugger.
I get the selenium server from openqa's repository, copy it into my maven build area with the dependency plugin, then start and stop it on the pre-integration-test and post-integration-test phases using antrun. On 8/10/06, Ralph Pöllath <[EMAIL PROTECTED]> wrote:
Hi, I understand that Selenium by design requires a full-fledged browser, but isn't that also one of its greatest features? By running your tests using FF or IE, you can be sure they do work in their target environment, regardless of browser bugs. So yes, the htmlunit approach makes testing easier to integrate with CI, but it doesn't give you the same results. This may be acceptable for many simple testcases though. I just looked over the jWebUnit 2.x website very quickly, so I may be missing something. But how is test case writing with jWebUnit easier than using Selenium's IDE or DSL syntax? Cheers, -Ralph. On 02.08.2006, at 10:02, Christophe DENEUX wrote: > Hi Daniel, > > Some advantages of using jWebUnit to test a web application are: > - easier test case writing, > - faster test case running, > - No graphic server is needed with the engine "htmlunit", so the > integration into a continuous integration system is easier (no > browser is needed), > - Soon, you will use an engine for Selenium to run your tests > directly in your browser. > > jWebUnit home: http://jwebunit.sourceforge.net > > ______________________________________________________________________ > ______ > > Christophe DENEUX / Capgemini Sud / Méditerranée > Technical Leader > Tel: + 33 4 93 72 43 74 / www.capgemini.com > Fax: + 33 4 93 21 02 95 > Porte de l'Arénas - Entrée B / 455 Promenade des Anglais / 06200 Nice > > Join the Collaborative Business Experience > ______________________________________________________________________ > ______ > > > > Daniel Serodio a écrit : >> Christophe DENEUX wrote: >> >>> Hi , >>> >>> A snapshot repository is available at: http://maven.openqa.org/ >>> >>> Have you try jWebUnit (http://jwebunit.sourceforge.net/index.html) >>> instead of Selenium for your functional tests? With jWebUnit, you >>> can >>> run your tests with different engines as htmlunit or Selenium (the >>> Selenium engine is available trough SVN). You will use the htmlunit >>> engine to execute your tests in a background mode (continuous >>> integration) and the selenium engine in a visual mode. >>> >> It's been a while since I looked at jWebUnit, and I'm currently using >> Selenium; what is the advantage of using jWebUnit as you describe >> instead of using Selenium directly? Do you have an URL with more >> info on >> the subject? >> >> TIA, >> Daniel Serodio --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
