[Webtest] Global page validation tests

Nate Oster Nate Oster" <noster@numbersix.com
Thu, 26 Oct 2006 11:33:49 -0400


This is a multi-part message in MIME format.

------_=_NextPart_001_01C6F914.23E43EED
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On my project, we have a set of global tests that should be true on
every page.  For example, every page should have a standard disclaimer
at the bottom, and a set of admin links.  In addition, we have negative
tests to ensure compliance with our UI standards, like that every table
column must have an HTML label, or that every Data Table should be in a
DIV of a certain class.

=20

What do you think is the best way to OPTIONALLY run a standard set of
WebTest steps (mostly VerifyXPath steps) against every page in the
application?  I tried <reportSite>, but of course that's simply a spider
that can only reach statically linked pages.  I'd prefer to simply "turn
on" the validation steps and have them run as part of our regular
functional test suites.

=20

In addition, it would be ideal if we could avoid failing the test script
if one of the expressions was violated, but instead simply log it as a
warning (much like warnings about XHTML compatibility is done now).
That way, you won't have to fix an issue in order to get the complete
set of validation failures as part of your regular test cycles.

=20

What do you think?

=20

Thanks!
Nate Oster


------_=_NextPart_001_01C6F914.23E43EED
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName" downloadurl=3D"http://www.microsoft.com"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>On my project, we have a set of global tests that =
should be
true on every page.&nbsp; For example, every page should have a standard
disclaimer at the bottom, and a set of admin links.&nbsp; In addition, =
we have
negative tests to ensure compliance with our UI standards, like that =
every
table column must have an HTML label, or that every Data Table should be =
in a DIV
of a certain class.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>What do you think is the best way to OPTIONALLY run a
standard set of WebTest steps (mostly VerifyXPath steps) against every =
page in
the application?&nbsp; I tried &lt;reportSite&gt;, but of course =
that&#8217;s
simply a spider that can only reach statically linked pages.&nbsp; =
I&#8217;d
prefer to simply &#8220;turn on&#8221; the validation steps and have =
them run
as part of our regular functional test =
suites.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>In addition, it would be ideal if we could avoid =
failing the
test script if one of the expressions was violated, but instead simply =
log it
as a warning (much like warnings about XHTML compatibility is done =
now).&nbsp;
That way, you won&#8217;t have to fix an issue in order to get the =
complete set
of validation failures as part of your regular test =
cycles.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>What do you think?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thanks!<br>
<st1:PersonName w:st=3D"on">Nate =
Oster</st1:PersonName><o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C6F914.23E43EED--