[Webtest] Verify Stylesheets

[Denis N. Antonioli]

On Wed, 2 Feb 2005, Marc Guillemot wrote:

> such an extension of <verifylinks /> could be interesting... but should probably work under an other name.

Any proposition?
<verifyLinkedContent>?

I've just had a very productive meeting, with plenty of time to think further about this ...
What we now have is a step 'verifyLinks' which crawls through a website and just
checks for 404.

Ideally, it should be renamed to <visitWebSite> and be a step container.
It would then apply all the contained steps to each pages:
<visitWebSite depth="2">
	<verifyLinkedContent xpath="//img" />
	<not><verifytext text="DB not available" /></not>
</visitWebSite>

Good old Visitor pattern...


> With such a strategy, checking all external references from a page could become messy. What about of introducing a new 
> concept of "filter" or something like that that would be executed on each page of a web sequence?

Yes, wouldn't that go in the direction 'action oriented programming for WebTest'?
That would be at least a good article ;-)

	dna