Hi Lisa,

Thanks for your response. The verifyXPath Step is the one I choosed to test the correctness of the page (and the XPath is simple, it's only checking for a known id). This test don't work, and when I print the response, the part of the page I search for is not in the content.

When i turn httpclient debug on, I see the ajax content in the page returned by the server. So Webtest does'nt take it as a new Response. Perhaps HtmlUnit list is a better way to post that, but I would like to get Advanced Webtest users' opinions before that

Thanks for reading

Florent

Pingwy
27, rue des arènes
49100 Angers



Lisa Crispin a écrit :
Hi Florent,
We were having what I think is a similar problem. We have a test that clicks a link to expand some details: We had to get just the right xpath:

          <verifyXPath description="verify the ajax text for the check"
          xpath="//t...@class='show']/div" />

Here's the html:

<tr class="shaded">

 <td id="panel304714" colspan="5" class="show">

 <div style="margin-left:3em;">
 <b>
 Requested Date:
 </b>

 04-13-2009, ... It wasn't the ideal thing to check for, but it only shows up if the link has been clicked, so it's "good enough" for us. Not sure if that helps you. We had tried the following, which did NOT work:
<verifyElementText description="verify match amt"
          type="div" text="Requested Date" />
-- Lisa
On Fri, Apr 10, 2009 at 9:40 AM, Florent Blondeau <[email protected] <mailto:[email protected]>> wrote:

    Hi there,

    Weird title, I know... But that's exactly what happens ! And for
    short, I can't give you some code
    to reproduce the error (too complex to synthetize)
    I come here to get your wise words about the ways it takes to make
    that happens.

    So, I test a page with lots of javascript. WebForms technology
    from Microsoft, and JQuery for most.
    I click on a link with a beautiful Id, and wait a few seconds to
    see appear a div triggered via an ajax call.
    Problem, the response I get doesn't include this div. Several
    things can be imagined here (javascript error,
    test error, typo error) but I turned on http.wire debug and
    something striked me :
    the page received on the wire is the good one !! The div is here,
    javascript submission has worked and ajax Call
    is successful.

    So !!! Why the response in Webtest (in HtmlUnit Webclient) is not
    the one that came on the wire ?

    Please help me to find out what happens really, I run out of ideas
    concerning debugs I can do

    Cheers

    Florent

-- Pingwy
    27, rue des arènes
    49100 Angers

    _______________________________________________
    WebTest mailing list
    [email protected] <mailto:[email protected]>
    http://lists.canoo.com/mailman/listinfo/webtest




--
Lisa Crispin
Co-author with Janet Gregory, _Agile Testing: A Practical Guide for Testers and Agile Teams_ (Addison-Wesley 2009)
http://lisacrispin.com

Reply via email to