[Webtest] Best way to determine "current response" (for bette r JS support)?

[Edgar P Dollin]

Absolutely.  There is so much in a page that can change post page load.

Edgar

> -----Original Message-----
> From: Marc Guillemot [mailto:mguillemot@yahoo.fr]
> Sent: Wednesday, November 17, 2004 4:44 AM
> To: webtest@lists.canoo.com
> Subject: [Webtest] Best way to determine "current response" 
> (for better
> JS support)?
> 
> 
> Hi,
> 
> with the increasing support for javascript it seems that 
> current way of considering "current" response is not more natural.
> 
> Current situation:
> The page on which steps (like verifyXXX, setXXX, ...) are 
> performed is - approximatively - the last one returned by an 
> invoke, a clicklink or a clickbutton (except for popups), a 
> followframe (perhaps do I forget some steps).
> This means for instance that responses loaded by a js 
> onchange event in a form or popups are never considered as the 
> current response.
> 
> A more "natural" way?
> Perhaps could we avoid saving a special response as the 
> "current" one and just consider the window that has the focus? 
> It would be a bit more difficult when frames are present but 
> no impossible.
> 
> Do I miss something or could we go in this direction?
> 
> Marc.
> 
> _______________________________________________
> WebTest mailing list
> WebTest@lists.canoo.com
> http://lists.canoo.com/mailman/listinfo/webtest
> 
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.788 / Virus Database: 533 - Release Date: 11/1/2004
>  
> 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.788 / Virus Database: 533 - Release Date: 11/1/2004