It depends what you want to use for an XHTML validator. If it is a java
one, it can probably be nicely integrated (and would be interesting in
WebTest itself, once integration is mature). It it is some executable
that you can only invoke on the command line, then integration will not
be as smart.
In both cases you can "simply" write a custom test to wrap this
functionality. This way you would still work in one "world". Webtest's one.
Marc.
Felipe Gaúcho wrote:
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 ....