[Webtest] [webtest][JIRA] Closed: (WT-452) verifyLinks - exclude option does not function

Marc Guillemot (JIRA) Marc Guillemot (JIRA)" <noreply@canoo.com
Thu, 24 Jul 2008 09:27:01 +0200 (CEST)

     [ http://webtest-community.canoo.com/jira/browse/WT-452?page=all ]
Marc Guillemot closed WT-452:

    Resolution: Invalid
     Assign To: Marc Guillemot

>From the doc for the excludes attribute: "If excludes is set then each link found is compared ..., if it matches then the link is not followed.". JS files aren't link (at least normally) therefore it doesn't apply for js files.

You can configure the options in Grails as well, have a look at the super class of your test and you'll see how it is setup and what you have to overwrite to configure it as you want.

Which version of the Grails-webtest plugin do you use? Normally prototype's drag & drop shouldn't cause any problem.

> verifyLinks - exclude option does not function
> ----------------------------------------------
>          Key: WT-452
>          URL: http://webtest-community.canoo.com/jira/browse/WT-452
>      Project: WebTest
>         Type: Bug

>     Versions: 2.6
>  Environment: Windows XP 2GB Ram , 30GB disk, JDK1.4 & JDK1.5, ANT 1.6.5
> Also fails on Tru64 32GB RAM, 4TB disk(s), HP JDK 1.4, ANT 1.6.5
>     Reporter: David Cate
>     Assignee: Marc Guillemot

> During invoking verifyLinks task, error message occurs based on Javascript file for script.aculo.us. 
> The link is
> I'm using XML in 1 branch and tried to exclude the file with "\\S*\\.js\\S*". I tested the regular expression and returned a true pattern match - but the task is not excluding the file. When I add 
> <config>
> <option name="ThrowExceptionOnScriptError" value="false" />
> </config>
> everything works fine.
> the primary branch of the project is written in GRAILS 1.0.2 and I would like to leverage the groovy power. However, the exclude doesn't work and access to the child element is unavailable. The Webtest.properties assumes the attributes of the config while the rest of the files assume a test level access with no access to the config modification that I can find.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see: