Hi, My company has decided to change all of the site to use JSON (javascript object notation). What this means in practice is that there is very little well formed content until after a page is rendered and all display JS is executed. Up until now, I have always disabled JS in my webtests due to some 3rd party JS in our pages; now I will have no choice but to run it!
So far, my preliminary testing has not been positive (testing with JS enabled, of course). I don't know why this is exactly. One possibility is that webtest is verifying page contents as they are served (what you see upon view source, e.g.) and not as they are rendered. Another possibility is that the xpath parser does not like the new structure. Using firefox (and its xpath parsing extensions, via DOM inspector), I can construct xpath statements just like like normal, and there doesn't seem to be a problem; using XPE, I get similar behavior as I get from webtest. So... 1. *should* webtest be analyzing rendered code if JS is enabled in webtest? 2. If not, is there a way I can induce that behavior? 3. Is it possible to use a more robust xpath engine/parser with webtest? 4. Does anyoe have any other recommendations for testing such a site? Thanks. Mike _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
