Unnsse, I've used Selenium which is the same idea as Watij in that it runs in a browser. (It uses a different browser - Firefox.) I like front end testing frameworks that run in the browser as that is where the "real" app runs.
Selenium is impressive (definitely check it out), but it does operate on a different level than HttpUnit. HttpUnit (and other, similar libraries like HtmlUnit and jWebUnit) are faster to set up and get going with, but they don't include tools that can create test code by watching a browser.
Unnsse, Selenium and Watij are both playback/record tools. Which means they support anything the browser can do.
You are correct that they are less "programmer" tools than HttpUnit, but that just means you are working at a higher level. Selenium provides hooks if you really want to write code. I find the playback/record mode easiest to use though.
Joined: Jan 23, 2002
Originally posted by Jeanne Boyarsky: Selenium and Watij are both playback/record tools. Which means they support anything the browser can do.
Actually, Watij is not a record/playback tool (or capture/replay or record/replay, whatever you want to call it). With Watij, just like with Selenium's "RC mode", you write tests by writing code and the code drives an actual browser instance. In the case of Watij, this is implemented by the Java code talking to the InternetExplorer COM object. In the case of Selenium, it's a bit more complex and involves the browser constantly downloading "commands" from an intermediary server.
In particular, watij is effectively a java clone of the ruby-based tool watir (one reason why the name of the original one sounds so much better)
One good way to find out what watij is all about is actually to read about watir.
And, of course, don't forget to add the original watir to your scriptable functional testing tools shortlist. Our test guys love watir, and have taken to scripting tests (and automating data loads, etc.) with it like ducks to, err, watir
Consideration to be taken care of, while using Watij :
1. Runs for IE till now, and NOT for any other browser. 2. Runs on Windows environment only 3. A JUNIT Wrapper over watij script may be a good way of execution. instead of beanshell. 4. Finally all can be automated in ANT build.
Joined: Jan 23, 2002
Originally posted by Unnsse Khan: In regards to Fitnesse, Selenium, Watij, HttpUnit, etc. - what I am seeking is a way to run one of these as a Ant target. Is this possible?
Of the above tools I've run Fit (not Fitnesse), Selenium and HttpUnit through Ant. For Fit, I basically used the <exec/> task and for Selenium and HttpUnit I used the <junit/> task (driving Selenium and HttpUnit from JUnit tests).