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/>
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Marc Guillemot
Sent: Tuesday, February 12, 2008 3:49 AM
To: [email protected]
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?
can you provide your whole <config> node?
Cheers,
Marc.
--
Blog: http://mguillem.wordpress.com
Klima, David wrote:
> That solution does not appear to work for me. Perhaps I am doing
> something incorrectly:
>
> 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.
>
> When I place
>
> <option name="ThrowExceptionOnFailingStatusCode" value="false"/>
>
> between the config start and end tags in the config.xml file, then run
> the test, I get a message saying config element must be followed with
> ">" or "/>"
>
> If I try it without the closed brackets, like this:
>
> option name="ThrowExceptionOnFailingStatusCode" value="false"
>
> I get a message saying that "option" needs an = sign after it.
>
> And when I experiment more in other ways, I get messages saying that
>
> config doesn't support name
>
> OR
>
> config doesn't support option.
>
> Does anyone have any suggestions?
>
> =============
>
> Hi Karel,
>
> you can use following:
>
> <config...>
> <option name="ThrowExceptionOnFailingStatusCode" value="false"/>
> </config>
>
> Marc.
>
> -----Original Message-----
> *From:* Klima, David
> *Sent:* Saturday, February 09, 2008 12:40 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?
>
> William,
>
> That looks like exactly what I need.
>
> Thank you.
>
> David Klima
>
> -----Original Message-----
> *From:* Soula, William [mailto:[EMAIL PROTECTED]
> *Sent:* Fri 2/8/2008 9:10 PM
> *To:* [email protected]; Klima, David
> *Cc:*
> *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?
>
> This one intrigued me and I first tried to use the <not> step
> around the <invoke..> and while this avoided the invoke failing
> I couldn't perform steps on the response as the failure reported
> to me was "No current response available! Is previous invoke
> missing?" which I found kinda amusing :) Then I went to the
> nabble page for the mailing list and searched "404 Not Found"
> and found Marc's reply to your exact question.
>
> http://www.nabble.com/How-to-test---verify-content-of-the-404-redirection-to12183398.html#a12183398
>
> Nabble is your best friend :)
>
> *William Soula*
> QA Analyst
>
> *Pointserve, Inc.*
> 110 Wild Basin Road
> Suite 300
> Austin, Texas 78746
> O: 512.617.5311
> F: 512.617.0466
>
>
>
> ------------------------------------------------------------------------
> *From:* [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] *On Behalf Of *Klima, David
> *Sent:* Friday, February 08, 2008 9:27 AM
> *To:* [email protected]
> *Cc:* Klima, David
> *Subject:* [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,
>
> As part of a test, I invoke a valid URL that is supposed to
> produce a 404 page not found error page because the logged-in
> user does not have privileges to view the specified URL. When I
> run the test, webtest records the invoke as a failing test, and
> my 2 subsequent steps to verify the title text and page text of
> the expected 404 page are apparently ignored, and not run, or do
> not get the passing results they should get. The last two steps
> have yellow bars next to them on the results page.
>
> 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?
>
> I would welcome any advice anyone may provide:
>
> Thanks Much,
>
> David Klima::
>
> *FROM MY XML FILE:*
>
> */ <invoke url="https://pretendurl.htm
> <https://pretendurl.htm/>"/*
> */ description="school case preparer cannot access
> FSA manage cycle page" /> /*//
>
> */ <verifyTitle text="HTTP 404 Not Found" />/*
> */ /*
> */ <verifyText text="The page cannot be found" />/*//
>
>
> *END: FROM MY FILE:*
>
>
>
>
>
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
Y��z�fj)b� b�՞m7��X����� �hm����+-�Ƨ��(����Y���b�ا~��y�^�
