Hi,
Please do not post on dev and users ml, as I think all dev are subscriber to both.
Concerning first point (relative high level of jWebUnit), the main purpose is to stay compatible with both HtmlUnit and Selenium. We can't use specific part of HtmlUnit API if it's not possible to do the same thing with Selenium. I'm open to any new method in jWebUnit API, as long as there is a chance to implement it with Selenium.
Concerning Exception mechanism... I totally agree with you. And it's in my todo list to completly refactor jWebUnit exception system, with more accurate exceptions (ElementNotFound, BadValue, ServerException, ...)
We could of course discuss the fonctionnalities you need, but try to be more precise (for example, open a new feature request for each new fonctionnality)
++
Julien
Please do not post on dev and users ml, as I think all dev are subscriber to both.
Concerning first point (relative high level of jWebUnit), the main purpose is to stay compatible with both HtmlUnit and Selenium. We can't use specific part of HtmlUnit API if it's not possible to do the same thing with Selenium. I'm open to any new method in jWebUnit API, as long as there is a chance to implement it with Selenium.
Concerning Exception mechanism... I totally agree with you. And it's in my todo list to completly refactor jWebUnit exception system, with more accurate exceptions (ElementNotFound, BadValue, ServerException, ...)
We could of course discuss the fonctionnalities you need, but try to be more precise (for example, open a new feature request for each new fonctionnality)
++
Julien
----- Message d'origine ----
De : "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
À : [email protected]; [email protected]
Envoyé le : Mardi, 1 Août 2006, 4h02mn 15s
Objet : [Jwebunit-users] Access to web client and windows
De : "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
À : [email protected]; [email protected]
Envoyé le : Mardi, 1 Août 2006, 4h02mn 15s
Objet : [Jwebunit-users] Access to web client and windows
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-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jwebunit-users
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-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jwebunit-users
------------------------------------------------------------------------- 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-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jwebunit-users
