Arquillian / Warp / WebDriver: How to treat 404/500 error? (and more)

[grubi]

Hi everybody,

I'm currently learning Arquillian + Warp to integrate unit tests in our JSF applications. Everything works quite well but a few annoying problems still exists.

1) A page that could not be found is not reported as an error. The tests will try to run as sepcified and everything will fail with a lot of exception (NoSuchElement, etc) that do not tell the real cause.

2) Exception from the server, that cause a 500 internal server error are not reported as an error. It is the same as 1)

3) Manipulation some request data like basic authentication.

4) Access to request data like status code or header fields is not possible?

Do you have any suggestions on how to solve each of these problems? Especially #1 and #2 complicates the implementation of unit tests or make it impossible.

Best regards

[grubi]

Next problem in conjunction with IE8 (*iexplore) and Graphene (other IE versions not tested):

After the Selenium Remote Control v2.24.1 poped up, a javascript error is thrown: Namespace "goog.Disposable" already declared.

So IE8 could not be used for automated testing, as the error message window has to be closed manually :/