Well, nobody seemed to have an answer to this so I dug and dug to work out what was going wrong. Turns out there's a bug in htmlunit which throws a null pointer exception when it shouldn't. The bug is fixed in htmlunit's subversion repository, so I guess it'll make it out into the rest of the world and hence into webtest in due course. I've built a fix which is working fine for me, and if anyone else wants it just let me know. (I haven't posted it because it doesn't seem to be an issue for anyone else at the moment.) Jon (talking to myself again :)
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon Davies Sent: 19 June 2007 17:46 To: [email protected] Subject: [Webtest] Problem with 204 No Content response I've been beginning to use canoo webtest on my current project, but have hit a problem: I have a page which under some circumstances returns a 204 No content http status code. But the tests I've built in webtest fail to run - (its not that they run and fail, but they they won't run and webtest dies). How can I run a test that expects a 204 status code, or is this a bug that I've found? Details below. Any help would be appreciated :) thanks Jon
