September 26, 2008 at 12:29 pm (HtmlUnit)
Tags: HtmlUnit 2.3
The HtmlUnit project is pleased to announce the release of HtmlUnit 2.3. This release brings another round of improvements and bug fixes (the release process has taken an unusual long time due to problems caused by SourceForge datacenter migration).
Here is an extract of the complete change log:
– better generics support to avoid casting
– improved JS support, particularly full support for GWT 1.5
– Firefox 3 now in the list of the simulated browsers
– a CookieManager
The generics improvements may require some simple code changes if you are using Sun Java 5 compiler due to a bug which has been fixed in Sun Java 6 compiler but not been back ported.
September 11, 2008 at 7:19 pm (NekoHTML)
Release 1.9.9 of NekoHTML is now available.
This release contains different bug fixes and improvements,
particularly in incorrect html code handling. Thanks to everyone who
contributed to this release.
Change log: here
September 10, 2008 at 12:26 pm (HtmlUnit, WebTest)
Tags: Google JS error, HtmlUnit, WebTest
Like many other testing tools, WebTest uses Google‘s website for simple code examples. It has the advantage to be a well known website, pretty fast and with simple code.
For some time WebTest users started to report that even simple examples from the demo tests available when creating a new project failed due to JS errors like this:
As this test used to work, this means that Google’s start page isn’t so simple any more that it used to be. It was predictable that this page would change one day but it is quite embarrassing as we use this kind of tests to show how easy and powerful WebTest is even for sites using a lot of JS stuff.
HtmlUnit‘s JS support is quite good (and improved continuously), but of course not (yet 😉 ) as good as the one of “real” browsers, therefore I’ve started to search for the cause of the problem in HtmlUnit, looking for missing/incorrect implementation of some JS functionalities. At the end I’ve found that the problem occurred only when setting directly the value attribute of the field rather than calling the
type(...) method on it because
keypress handlers were being used. This means that WebTest should probably use
type(...) rather than setting the field’s value directly.
But this means as well that Google’s home page relies on the
- – go to http://www.google.com/ncr (to be sure to have the English version of the page)
- – right mouse click in the search field to paste some value to search for
- – click the “I’m Feeling Lucky” button
The results are quite similar to the JS error obtained by WebTest, no matter if you use Firefox or Internet Explorer (perhaps does it work correctly with Chrome 😉 ):
Rather painful for Google than for WebTest!
OK, this error is nothing dramatical but for an Internet giant like Google that has plenty of talented engineers (and …, and…, and …. You perhaps know better than I what the web means for Google), I find quite painful to have such an error on its main page!
The error scenario is not particularly complicated and such a case should surely be covered by automated tests. Perhaps is it a question of inadequate tools? Google seems to use intensively Selenium 😉 .
Concerning WebTest, I’ll start the discussion on the mailing list to decide what is the best way to follow: setting directly the field value, typing it, or having both possibilities.