Hi David,
I had a similar problem late last week, some JavaScript
files where changed on a public website I use verifyLinks on, but whose
content I do not control. I got around the JavaScript error, by
disabling the JavaScript validation via the config setting (i.e. note
the ThrowExceptionOnScriptError option set to false):
<config host="${host}" port="${port}" protocol="http"
basepath="${webapp.name}" resultpath="${resultPath}"
saveresponse="true"
resultfile="web-tests-result.xml" summary="true">
<header name="Accept-Language" value="${user.language}"/>
<option name="ThrowExceptionOnScriptError" value="false" />
</config>
This may be too drastic for you, in that you may want to see JavaScript
errors. However, it's good to know this can be a solution to you, if you
don't get another from someone else.
HTH,
Conor
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, 23 July 2008 8:07 AM
To: [EMAIL PROTECTED]
Subject: [Webtest] VerifyLinks
I have a site that I am testing with the following:
<verifyLinks depth="11" onsiteonly="true" excludes=".*js.*"/>
I want to test 11 levels deep and ignore any javascripts files. I'm
still receiving errors for the following:
http://127.0.0.1:8080/js/prototype/dragdrop.js#600
I thought it would skip over this file since i didn't want it looked
after.
Also, does anyone have good examples of using reportLinks and
ReportSite? Not quite sure the difference between the 2 except that
reportSite appears to work if you provide the sub element and
reportLinks just seems to short-circuit to true.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This email (including any attached files) is for the intended
recipient(s) only. If you received this email by mistake, please,
as a courtesy, tell the sender, then delete this email.
The views and opinions are the originator's and do not necessarily
reflect those of the Queensland Studies Authority. All reasonable
precautions have been taken to ensure that this email contained no
viruses at the time it was sent.
