April 21, 2009 at 10:37 am (HtmlUnit, NekoHTML)
The HtmlUnit team is pleased to announce the release of HtmlUnit 2.5. This release brings another round of improvements and bug fixes.
Here is an extract of the change log:
March 2, 2009 at 10:11 am (HtmlUnit)
Great news: the proposal of HtmlUnit committers Daniel Gredler and Ahmed Ashour for the next JavaOne conference has been accepted!
They will present ” HtmlUnit: An Efficient Approach to Testing Web Applications ” at the biggest Java conference in San Francisco (May 31 – June 05).
This is an additional very good sign for the constantly growing recognition of HtmlUnit and I hope that it will be the occasion for them to meet a lot of HtmlUnit users.
January 9, 2009 at 10:07 am (HtmlUnit)
Tags: Apache Foundation, HtmlUnit
Should HtmlUnit move to Apache Foundation? (the first step would be to make a proposal for the Apache Incubator)
Nothing is decided, we’re just thinking loud and are interested to hear what our users think of this idea. I’ve started the discussion in HtmlUnit user mailing list but comments are welcome here too.
January 9, 2009 at 9:56 am (HtmlUnit)
Tags: HtmlUnit, TheServerSide Symposium
I will present “HtmlUnit: An Efficient Approach to Testing Web Applications” together with Daniel Gredler at TheServerSide Java Symposium in Las Vegas (March, 18).
This will be funny because I work together with Daniel in the HtmlUnit project since a few years and I’ve never met him until now.
I think that this will be a great occasion to show HtmlUnit’s potential and I hope that we will meet a lot of HtmlUnit users.
Thanks to Tools & Techniques chair Frank Cohen for inviting us.
December 30, 2008 at 1:42 pm (HtmlUnit, NekoHTML)
The HtmlUnit project is pleased to announce the availability of the HtmlUnit 2.4 release.
This release brings another round of improvements and bug fixes. This should have been a Christmas relase but a regression found in NekoHtml-1.10 forced us to wait a bit.
Here is an extract of the change log:
- improved JS support, particularly full support for the AJAX libraries JQuery and MochiKit
- possibility to use real ActiveX objects (on windows only)
- minimal applet support
- support for IE conditional comments
December 3, 2008 at 8:14 am (HtmlUnit, Test Automation)
Tags: HtmlUnit, MochiKit
The library’s own tests are integrated in HtmlUnit’s build and they now all (2) pass, no matter if we simulate Firefox 2, Firefox 3, Internet Explorer 6 or Internet Explorer 7. This time, it was not so complicated to reach 100% support: fix a bug in Rhino, implement a dummy support for the filters property on HTML elements when simulating IE, handle detached nodes for offsetParent, and fix a few things in computing CSS properties.
I believe that we’re on the right way and that we’ll soon be able to announce full support for other well known libraries.
(1) I suppose here that the library’s own tests are representative for the library usage.
(2) In fact we run only the tests files that pass in a “real” browser and therefore have to ignore 3 files.
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.
August 26, 2008 at 3:26 pm (HtmlUnit, Test Automation, WebTest)
Tags: HtmlUnit, JUG Cologne, WebTest
Here are the slides of the presentation I’ve made yesterday:
July 24, 2008 at 3:36 pm (HtmlUnit)
The HtmlUnit team is pleased to announce the release 2.2 of HtmlUnit.
This release contains numerous improvements and bug fixes, particularly in handling of ill formed HTML code and in AJAX support as well as noticeable speed gains making it even faster in different situations.
July 22, 2008 at 4:04 pm (HtmlUnit, Test Automation)
Tags: Celerity, HtmlUnit, schnell, Watir
After Celerity, a new open source JRuby library, schnell, uses HtmlUnit to provide a fast Watir-like API for functional testing of web applications. According to the announcement, it runs… 37,5 times faster than Watir!
(thanks Daniel for the info)