« Return to Thread: Upgrading from R_1454 to R_1600

Re: Upgrading from R_1454 to R_1600

by Marc Guillemot :: Rate this Message:

Hi Matt,

I will try to investigate this as you've provided a public url where the problem occurs.

I imagine that more js code gets evaluated now but that for some reason it blocks evaluating something that wasn't evaluated at all before.

More in the coming days (I hope)...

Concerning log configuration: you have to be sure that the log4j configuration file is in the classpath used to load the WebTest libs. This is automatically the case if you make use of WebTest's webtest.xml (what is recommanded).

Marc.

It appears that something changed between HtmlUnit 1.11 and 1.12 that breaks this test. If I use Canoo WebTest R_1600 with HtmlUnit 1.11, the test passes. If I use HtmlUnit 1.12 or 1.13, the test fails. Should I enter an issue in WebTest's JIRA or HtmlUnit's?

Matt

Here's a test to reproduce the problem. With 1454 it passes, with 1600 it fails:

<target name="list">
<webtest name="userTests">
<config host="demo.appfuse.org" port="80" protocol="http" basepath=""
resultpath="target/data" resultfile="web-tests-result.xml"
summary="true" saveresponse="true"/>
<steps>
<invoke url="/appfuse-jsf/users.html"/>
<setinputfield description="set user name" name="j_username" value="admin"/>
<setinputfield description="set password" name="j_password" value="admin"/>
<clickbutton label="Login" description="Click the submit button"/>
<verifytitle text="User List | AppFuse"/>
<clicklink xpath="//table[@id='editUser:users']/tbody/tr[1]/td[1]/a"/>
<verifytitle text="User Settings | AppFuse"/>
</steps>
</webtest>
</target>

Matt

mraible wrote:

I've tried cranking up log4j.xml to have com.gargoylesoftware.htmlunit=DEBUG, but that doesn't seem to help.

Matt

John and Pip wrote:

Hi Matt,

You should be able to increase the logging level in the log4j properties
file probably in lib folder.

I sometimes get this type of problem if I've turned javascript error
checking off in webtest and then there is an error which means the
javascript that clicks that link is not loaded and so doesn't run. Have you
turned jscript error checking off?

cheers,
John

On 8/28/07, mraible <matt@raibledesigns.com> wrote:
>
>
> Is it possible to crank up logging to see why clicking the link is
> failing?
> Like I said, I haven't changed any code and it worked with the previous
> release.
>
> Thanks,
>
> Matt
>
>
> mraible wrote:
> >
> > I'm trying to upgrade from R_1454 to R_1600. With 1454, I had a JSF
> > dataTable that used a commandLink to edit a record. This command link
> > would submit a JavaScript form. For some reason, this is no longer
> working
> > with R_1600. There's no error or anything, it just never makes it to my
> > edit page. Any ideas?
> >
> > The content of the generated HTML hasn't changed.
> >
> > Thanks,
> >
> > Matt
> >
>
> --
> View this message in context:
> http://www.nabble.com/Upgrading-from-R_1454-to-R_1600-tf4319687.html#a12354180
> Sent from the WebTest mailing list archive at Nabble.com.
>
> _______________________________________________
> WebTest mailing list
> WebTest@lists.canoo.com
> http://lists.canoo.com/mailman/listinfo/webtest
>

« Return to Thread: Upgrading from R_1454 to R_1600