Hi folks,
I added a post-testing step to validate my XHTML
<target name="webtest:verify-xml" description="validates the XML pages
against the DTDs">
<echo message="Validating the server XML responses ..."/>
<xmlvalidate failonerror="yes">
<fileset dir="${webtest.response.dir}" includes="**/wap*.html" />
<xmlcatalog>
<dtd publicId="-//W3C//DTD XHTML Basic 1.0//EN"
location="${webtest.dtd.dir}/xhtml-basic/xhtml-basic10.dtd"/>
<dtd publicId="-//WAPFORUM//DTD XHTML Mobile 1.0//EN"
location="${webtest.dtd.dir}/xhtml-mobile/xhtml-mobile10-flat.dtd" />
<dtd publicId="-//WAPFORUM//DTD WML 2.0//EN"
location="${webtest.dtd.dir}/wml20/wml20-flat.dtd"/>
</xmlcatalog>
</xmlvalidate>
</target>
Cheers,
Siegfried Goeschl
Pedro Pinto wrote:
Hi,
i once had a similar problem and the simplest solution i thought of was
saving the html response code in a ant property and then using another
webtest inside the same ant target to call up W3C online validator. This
isnt by far the best solution, but it worked...
thanks for your reply,
If you have a "good" XHTML validator, it shouldn't be difficult to bind
it with WebTest.
how to do that ? where to find information about that ?
I am trying to keep webtest as the default testing mechanism.. I know
I can use other tools for testing compatibility, but then I will adopt
different worlds in my project with maintenance side-effects ....
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
