[Webtest] VerifyLinks

david.cate@wachovia.com david.cate@wachovia.com
Wed, 23 Jul 2008 08:56:29 -0400


This is a multipart message in MIME format.
--=_alternative 004719028525748F_=
Content-Type: text/plain; charset="US-ASCII"

Well, each page will get tested individually, and the JS isn't foreign(I'm 
assuming that means foreign to the site domain) - it's script.aculo.us - 
works pretty well with the Grails website. There's just an error in some 
3rd party code and we would be better off to ignore it for the spider. 
Like i said, each page will get tested after that step.

I'm still curious as to the differences between verifyLinks, reportSite, 
and reportLinks.




Marc Guillemot <mguillemot@yahoo.fr> 
Sent by: webtest-admin@gate4.canoo.com
07/23/2008 03:51 AM
Please respond to
webtest@gate4.canoo.com


To
webtest@gate4.canoo.com
cc

Subject
Re: [Webtest] VerifyLinks






what about ignoreForeignJSErrors?
http://webtest.canoo.com/webtest/manual/verifyLinks.html

Cheers,
Marc.
-- 
Blog: http://mguillem.wordpress.com


Conor MacMahon wrote:
> 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:* webtest-admin@lists.canoo.com
> [mailto:webtest-admin@lists.canoo.com] *On Behalf Of
> *david.cate@wachovia.com
> *Sent:* Wednesday, 23 July 2008 8:07 AM
> *To:* webtest@gate4.canoo.com
> *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.

_______________________________________________
WebTest mailing list
WebTest@lists.canoo.com
http://lists.canoo.com/mailman/listinfo/webtest


--=_alternative 004719028525748F_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Well, each page will get tested individually,
and the JS isn't foreign(I'm assuming that means foreign to the site domain)
- it's script.aculo.us - works pretty well with the Grails website. There's
just an error in some 3rd party code and we would be better off to ignore
it for the spider. Like i said, each page will get tested after that step.</font>
<br>
<br><font size=2 face="sans-serif">I'm still curious as to the differences
between verifyLinks, reportSite, and reportLinks.</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Marc Guillemot &lt;mguillemot@yahoo.fr&gt;</b>
</font>
<br><font size=1 face="sans-serif">Sent by: webtest-admin@gate4.canoo.com</font>
<p><font size=1 face="sans-serif">07/23/2008 03:51 AM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
webtest@gate4.canoo.com</font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">webtest@gate4.canoo.com</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [Webtest] VerifyLinks</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>what about ignoreForeignJSErrors?<br>
http://webtest.canoo.com/webtest/manual/verifyLinks.html<br>
<br>
Cheers,<br>
Marc.<br>
-- <br>
Blog: http://mguillem.wordpress.com<br>
<br>
<br>
Conor MacMahon wrote:<br>
&gt; Hi David,<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; I had a similar problem
late last week, some JavaScript<br>
&gt; files where changed on a public website I use verifyLinks on, but
whose<br>
&gt; content I do not control. I got around the JavaScript error, by<br>
&gt; disabling the JavaScript validation via the config setting (i.e. note<br>
&gt; the ThrowExceptionOnScriptError option set to false):<br>
&gt; &nbsp;<br>
&gt; &lt;config host=&quot;${host}&quot; port=&quot;${port}&quot; protocol=&quot;http&quot;<br>
&gt; &nbsp; &nbsp; basepath=&quot;${webapp.name}&quot; resultpath=&quot;${resultPath}&quot;
saveresponse=&quot;true&quot;<br>
&gt; &nbsp; &nbsp; resultfile=&quot;web-tests-result.xml&quot; summary=&quot;true&quot;&gt;<br>
&gt; &nbsp; &nbsp; &lt;header name=&quot;Accept-Language&quot; value=&quot;${user.language}&quot;/&gt;<br>
&gt; &nbsp; &nbsp; &lt;option name=&quot;ThrowExceptionOnScriptError&quot;
value=&quot;false&quot; /&gt;<br>
&gt; &lt;/config&gt;<br>
&gt; &nbsp;<br>
&gt; This may be too drastic for you, in that you may want to see JavaScript<br>
&gt; errors. However, it's good to know this can be a solution to you,
if you<br>
&gt; don't get another from someone else.<br>
&gt; &nbsp;<br>
&gt; HTH,<br>
&gt; Conor<br>
&gt; <br>
&gt; ------------------------------------------------------------------------<br>
&gt; *From:* webtest-admin@lists.canoo.com<br>
&gt; [mailto:webtest-admin@lists.canoo.com] *On Behalf Of<br>
&gt; *david.cate@wachovia.com<br>
&gt; *Sent:* Wednesday, 23 July 2008 8:07 AM<br>
&gt; *To:* webtest@gate4.canoo.com<br>
&gt; *Subject:* [Webtest] VerifyLinks<br>
&gt; <br>
&gt; <br>
&gt; I have a site that I am testing with the following:<br>
&gt; <br>
&gt; &lt;verifyLinks depth=&quot;11&quot; onsiteonly=&quot;true&quot; excludes=&quot;.*js.*&quot;/&gt;<br>
&gt; <br>
&gt; I want to test 11 levels deep and ignore any javascripts files. I'm<br>
&gt; still receiving errors for the following:<br>
&gt; <br>
&gt; http://127.0.0.1:8080/js/prototype/dragdrop.js#600<br>
&gt; <br>
&gt; I thought it would skip over this file since i didn't want it looked
after.<br>
&gt; <br>
&gt; Also, does anyone have good examples of using reportLinks and<br>
&gt; ReportSite? Not quite sure the difference between the 2 except that<br>
&gt; reportSite appears to work if you provide the sub element and<br>
&gt; reportLinks just seems to short-circuit to true.<br>
<br>
_______________________________________________<br>
WebTest mailing list<br>
WebTest@lists.canoo.com<br>
http://lists.canoo.com/mailman/listinfo/webtest<br>
</tt></font>
<br>
--=_alternative 004719028525748F_=--