Update to latest HtmlUnit snapshot to fix URL encoding bug about celerity HOT 4 CLOSED

Yes, this should resolve itself as soon as we're able to do a release with the snapshots currently in HEAD. There are other issues with the snapshots though (which you'll see if you run the specs).

from celerity.

Pushed some things to the "ticket19" branches of my forked repos:

• http://github.com/wincent/celerity/commits/ticket19
• http://github.com/wincent/watirspec/commits/ticket19

First up, found that the specs in browser_spec.rb were hanging indefinitely, so I tried running individual spec files to see if the other specs passed and found that some of them couldn't be run individually. This commit fixes that:

http://github.com/wincent/celerity/commit/a31f0c383a3b9904bef898a85b3c3a62edef638c

I'm also seeing 1 failure in watir_compatibility_spec.rb, and 1 failure in watirspec/button_spec.rb. Both failures show errors like this in the console:

[2010-06-22 15:23:29] ERROR ArgumentError: negative length -35 given

Not sure why the browser_spec.rb specs are hanging, anyway. Basically hangs after about 10 examples with the last thing being visible this:

[2010-06-22 15:19:47] INFO  going to shutdown ...
[2010-06-22 15:19:47] INFO  WEBrick::HTTPProxyServer#start done.

If I mark the hanging example as "pending", the next one hangs, and so on...

In any case, added a spec for the bug under discussion in this ticket:

http://github.com/wincent/celerity/commit/b4032fc2b12398264902735a3f7e8216cc3ac62c

Note that this depends on a change in the submodule:

http://github.com/wincent/watirspec/commit/050d6f8084fe9ac34619637ca3e8cf699142cd26

I did not bother updating the superproject because the commit hash will most likely be different when/if you merge it in anyway, so I'll leave that up to you.

from celerity.

Thanks, I've pulled in your changes.

The hanging spec is known, and is caused by the previous "huge page" specs. HtmlUnit recently introduced a new page type that needs to be dealt with - I'm working on it :)

I'm unable to reproduce the failures in watir_compatibility_spec.rb and watirspec/button_spec.rb. Could you open a new ticket for those with the full backtrace + info about your JRuby environment (OS, JDK etc)?

from celerity.

Opened a ticket with the info for those other spec failures:

http://github.com/jarib/celerity/issues/issue/20

Cheers,
Wincent

from celerity.