Wednesday, January 24, 2007
WATIN vs WATIR
I've been messing about with WATIR for awhile now and am very impressed. Very powerful, very flexible and I love any excuse to learn a new language (ruby). However, most of my coworkers do not share my thirst for knowledge. Nobody seamed interested in the amazing things that I was doing. Guess they were to busy getting the bug count down, forget that what I'm doing could keep it from getting high in the first place. Knowing this I've moved on to WATIN which so far seems to have most of the same features comes with an IDE and intellisense. Oh and lets not forget the US Navy and its list of approved software. The couple of DLLs that make up watin can be included in a project, but I don't think that an entire interpreter could be thought of in the same way.
Subscribe to:
Post Comments (Atom)
5 comments:
Have you tried SWExplorerAutomation SWEA (http:\\webiussoft.com)? SWEA is not an open source, but you can save a lot of time if you use SWEA to develop the unit tests.
I did try SWEA and it was easy to create the tests, however I think that the WATIR/WATIN programming model is easier to understand at the code level.
Check out InCisif.net.
InCisif.net is an automation tool designed to implement client-side functional testing of web applications under Internet Explorer 6.x or 7.x, using the C# or VB.NET language with Visual Studio 2003, 2005 or express editions.
InCisif.net
SWEA programming model is more advanced than WATIR/WAIT programming model. The UI usually changes often. In the case of WATIN/WATIR the script(s) should be updated which can be very time consuming task. SWEA allows visually rebind a control binding (SWEA project file) without script changes and one SWEA project can be used to record many tests.
Post a Comment