I love these Proof Of Concept rants by management when it comes to selecting test tools
Step 1. Is the web code you're testing compliant to its doctype specifier? You can check at validator.wc.org. If it's not ask the development and management team what standard they follow and why they don't work to any standard to output web pages. If development is shooting from the hip why can't test? If the web code is compliant then testing with any commerical or open source product will work where the impact is based on the learning curve of the test product. Watir has a very easy learning curve with good proficiency in a matter of weeks Step 2. Characterize the application under test. Are you using any third party controls like flash, applets, or is it GWT? This may be a problem WATIR doesn't support flash, GWT is just plain obnoxious to work through. Step 3. For proof of concept a simple login/logout and maybe simple data retrieval or entry is enough. You did get the simple watir exercise of the google search to work correct? Step 4. Goto http://watir.com/ and look at the Watir Users logos. All those players found Watir a valuable enough tool to let them use their name -- Is that a concept or what! Step 5. Enjoy. Read, learn and keep trying. -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. [email protected] http://groups.google.com/group/watir-general [email protected]
