Greetings, Posting to dev and user forums because it addresses both communities....
Yesterday I started migrating to 1.3 of jwebunit replacing the httpunit with htmlunit. In the refactored design I am having trouble getting to some items that I used to get to in the old version. How does one get access to the response information such as status, message, etc.? I understand that the refactored design (from reading the code and javadocs) wants to isolate the user from the underlying testing engine. However, sometimes I need to get to the lower level information so I can check the protocol being used, response status codes, etc. Also, in doing "negative" testing I often produce invalid requests to make sure my error handling is working correctly. I liked the way that 1.2 allowed you to catch the testing engine's exceptions. Instead I have to catch the assert exception and parse out the information from the message. Should I extend the htmlunit plugin to expose the functionality I need? I don't think the subclassing will help with getting access to the raw exceptions, however. I appreciate your thoughts or any other user's workarounds they have found. Regards, Jim Open Source Contributor -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ . ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Jwebunit-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jwebunit-development
