Hi folks, I'm picking up a thread of Eric Pugh ... "Canoo Webtest and Yet Another Testing Tool" and clarification of its usage.
When we talk about testing we have a few choices +) Do not test at all ... if you do that you can stop reading and save some time (that +you need for field testing anyway) +) Unit Testing (White Box Testing) is usually done with JUNIT +) Integration Testing might be done with JUNIT, JUNITPP and CACTUS +) End-To-End Testing, Functional Testing, Black Box Testing - Testing is not done +with successful integration test. Your user might find that he/she can't login since +the login button is missing and you should be able to find that automatically. I know +that's a stupid (but real life) example BUT a HTTPUnit Test succeeded since it does +not need the submit button for the login. The Canoo Webtest script reported an error +since it was not able to click on the non-existing login button .. cool +) The next step on the testing evolution ladder are load/stress tests - for webapps I +use Microsofts Web Application Stress Tool and openSTA. These are capture and replay +tools and great to hammer (and to kill) a web application (only if the application +does not encode a session id into every URL but uses cookies instead). If you would +like to improve your performance you need to run a performance profiler while +hammering the server - and then analysze the results of the profiling. If you are +carving out a living as consultant you can go for the quick kill by looking at +logging statements and String.concat() in the server code ... :-) +) If you are really serious about testing you take your test coverage into account - +done with commercial tools such as JProbe or Clover ... I look out for QUILT as an +OSS alternative. Consequently I don't see Canoo Webtest as a YATT but as tool for better test automation ... Thanks Siegfried Goeschl -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
