morgand 02/01/18 12:13:17
Modified: latka/tests/latka-self-test TestLatka.xml
Log:
fixed response header test and outdated comments
Revision Changes Path
1.13 +9 -22 jakarta-commons/latka/tests/latka-self-test/TestLatka.xml
Index: TestLatka.xml
===================================================================
RCS file: /home/cvs/jakarta-commons/latka/tests/latka-self-test/TestLatka.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- TestLatka.xml 10 Jan 2002 22:39:38 -0000 1.12
+++ TestLatka.xml 18 Jan 2002 20:13:17 -0000 1.13
@@ -3,7 +3,12 @@
<suite defaultHost="${defaultHost}" defaultPort="${defaultPort}"
label="Latka self-diagnostics">
- <!-- functional tests that Latka can run on itself -->
+ <!--
+ functional tests that Latka can run on itself,
+ using JSPs included in the Latka webapp.
+ You can actually run this test from the web interface
+ to have the webapp test its own jar. :)
+ -->
<!-- START HEADER CHECKS -->
<session>
@@ -57,8 +62,9 @@
<request path="${latkaContext}/self-test/snoop/RequestHeaders.jsp"
label="case-insensitive headers">
<validate>
- <responseHeader headerName="Content-length"/>
- <responseHeader headerName="content-LENGTH"/>
+ <responseHeader headerName="Date" label="Date spelling"/>
+ <responseHeader headerName="date" label="date spelling"/>
+ <responseHeader headerName="dATE" label="dATE spelling"/>
</validate>
</request>
@@ -68,13 +74,6 @@
<!-- START SESSION TESTS -->
- <!--
- our version of HttpClient is flawed - it can only accept up to one
- cookie from the server. Therefore our session functionality is
- virtually guaranteed to fail until the problem is fixed. We're
- waiting for the new version of HttpClient to be released, which
- will fix this problem.
- -->
<!-- verify that cookies are preserved correctly -->
<session sessionId="corporatePants">
@@ -93,12 +92,6 @@
<regexp pattern="Cookie added; name=foo; value=bar"/>
<regexp pattern="Cookie path: /"/>
<regexp pattern="Cookie domain: localhost"/>
- <!--
- this will probably fail in the current version of
- httpclient, which will only set a maximum of one
- cookie per request (and every Tomcat request sets
- a cookie for the session)
- -->
<cookie name="foo" value="bar"
label="verify that HttpClient assigned 'foo' cookie to the session"/>
</validate>
@@ -185,11 +178,6 @@
<!-- START BASIC AUTH TESTS -->
- <!--
- does not work. HttpClient throws an exception rather than returning a 401
- seems wrong, because unauthorized ne error. note that httpclient does NOT
- throw an exception for a 403
- -->
<request path="${latkaContext}/self-test/basicAuth/Login.jsp" label="not logged
in">
<validate>
<statusCode code="401" label="Without credentials, status code should be
401"/>
@@ -223,7 +211,6 @@
</validate>
</request>
- <!-- not sure why this fails -->
<session sessionId="authSession">
<request path="${latkaContext}/self-test/basicAuth/Login.jsp"
label="credentials in a cached session">
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
