Oh yeah, close it with </config> instead of <config/> so it looks like below:

<config
       host="localhost"
       port="8080"
       protocol="http"
       basepath=""
       summary="true"
       saveresponse="true"
       resultfile="${wt.resultfile}"
       resultpath="${wt.resultpath}"
       haltonfailure="false"
       haltonerror="false">
       <option name="ThrowExceptionOnFailingStatusCode" value="false"/>
  </config>

I have gotten the following code to work correctly surrounded by appropriate 
tags of course:

<config host="www.google.com<blocked::http://www.google.com/>" protocol="http" 
port="80">
    <option name="ThrowExceptionOnFailingStatusCode" value="false"/>
   </config>
    <invoke url="/pics/loginfiles"/>
   <verifyTitle text="404 Not Found"/>

If you still can't get it to work with your current test try creating a new 
webTest test file and use this example.

William Soula
QA Analyst

Pointserve, Inc.
110 Wild Basin Road
Suite 300
Austin, Texas 78746
O: 512.617.5311
F: 512.617.0466


________________________________
From: Klima, David [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 12, 2008 12:09 PM
To: Soula, William; [email protected]
Cc: Klima, David
Subject: RE: [Webtest] Is there a way for webtest to verify title text and page 
text of an expected 404 page produced by an expected and desired failed URL 
invoke step?

Hi, William, (and everyone else in the webtest community)--

Thanks for the suggestion--

I gave it a try, and with my config.xml setup just like the example below, when 
I ran my test, the build failed with a message that said:

"XML document structures must start and end within the same entity"

I have experimented a lot, and have not found a way to run a test with the 
following line:

<option name="ThrowExceptionOnFailingStatusCode" value="false"/>

in between the config start and end tags in my config.xml file.  An error has 
always been thrown.

I am trying to use webtest to verify title text and page text of an expected 
404 page produced by an expected and desired failed URL invoke step.

Any suggestions, direction, or insight would be very much appreciated.

Thanks!

David Klima


-----Original Message-----
From: Soula, William [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 12, 2008 9:08 AM
To: [email protected]; Klima, David
Subject: RE: [Webtest] Is there a way for webtest to verify title text and page 
text of an expected 404 page produced by an expected and desired failed URL 
invoke step?


Try putting a closing ">" on your config setup like I have done for you below.  
I enlarged the font of it so you could see.

<config
        host="localhost"
        port="8080"
        protocol="http"
        basepath=""
        summary="true"
        saveresponse="true"
        resultfile="${wt.resultfile}"
        resultpath="${wt.resultpath}"
        haltonfailure="false"
        haltonerror="false">
        <option name="ThrowExceptionOnFailingStatusCode" value="false"/>
   <config/>


William Soula
QA Analyst

Pointserve, Inc.
110 Wild Basin Road
Suite 300
Austin, Texas 78746
O: 512.617.5311
F: 512.617.0466

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Klima, David
Sent: Tuesday, February 12, 2008 7:57 AM
To: [email protected]; Marc Guillemot
Cc: Klima, David
Subject: RE: [Webtest] Is there a way for webtest to verify title text and page 
text of an expected 404 page produced by an expected and desired failed URL 
invoke step?

Hi, Marc,

Below is the contents of my config.xml file.  Is this what is called the config 
node?

I will appreciate any insight and/or advice you may offer.

Thanks!

David Klima::


<!--
Like all files of this folder, this content will be available as entity using 
the DTD (here &config;)
-->
<config
        host="localhost"
        port="8080"
        protocol="http"
        basepath=""
        summary="true"
        saveresponse="true"
        resultfile="${wt.resultfile}"
        resultpath="${wt.resultpath}"
        haltonfailure="false"
        haltonerror="false"
        <option name="ThrowExceptionOnFailingStatusCode" value="false"/>
   <config/>



...Continued but deleted to save space...

Reply via email to