Bugs item #1744626, was opened at 2007-06-28 07:06
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=497982&aid=1744626&group_id=61302

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: HtmlUnit plugin
Group: Release 1.4.1
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Matthew Jensen (mmj123)
Assigned to: Nobody/Anonymous (nobody)
Summary: Http 404's produce exceptions

Initial Comment:
In some test cases we expect 404's and would like to continue processing the 
web conversation as normal.  JWebunit 1.4.1 throws an exception on gotoPage 
(and other navigation methods) when the result is a 404.

JWebunit 1.2 did not do this, I believe this behavior should be at least 
optional.

Status code 404's are normal within out application and should be tested like 
any other page and doesn't indicate a fatal error.  This is true for all other 
http error codes, it should be up to the test to assert on the expected status 
code.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=497982&aid=1744626&group_id=61302

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
JWebUnit-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jwebunit-development

Reply via email to