Hi Ruel,
I also work with dynamic pages where a lot is constructed via JS / AJAX.
I'm not an experienced WebTest user, but I already learned my first lessons. ;-)
I have two proposals for you:
1) Simple: Add a <sleep> element directly after the element triggering the
request
for the page (<invoke> or <clickElement> or whatever).
2) More elaborated:
<retry ...>
<sleep .../>
<verify... > ==> Check here for something which is only
available when the whole page is completed by JS.
</retry>
Hope that helps
Rolf
Loehr, Ruel wrote:
I’m a beginner, but have searched through the list and still can’t find
the right answer. Maybe you can point me in the right direction.
A webpage I am attempting to test has a javascript function which
inserts a few rows into a table. If I view the source of the page, the
rows do not exists in the source as they are added dynamically.
Is there a reasonable way to access these rows from the table via webtest?
In a similar post marc said:
Due to improvements for
1 or 2 weeks, current state of a page is dumped to the filesystem
exactly like server responses when js code modifies the page structure.
Can we force webtest to look in these files and parse them or something?
**Ruel Loehr**
Configuration Management
**Pointserve, Inc.**
110 Wild Basin Road
Suite 300
Austin, Texas 78746
O: 512.617.5314
F: 512.617.0466
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
