Loadrunner korreliert IDs, die im Abschnitt EXTRAES in web_URL vorkommen

608
Anna

Ich arbeite an loadrunner, um eine Webanwendung mithilfe des Web-Protokolls http \ html aufzuzeichnen.

Die "WindowID", die in einer Transaktionsanforderung verwendet wird, befindet sich im vorherigen Abschnitt "web_url - Extraes". Wie können wir die "Fenster-ID" erfassen, die im Abschnitt EXTRAES vorkommt.

Die "Fenster-ID" tritt in der GET-Anforderung auf

GET / services / rest / lps / ComponentService / config / 305? _Dc = 1457259096313 & windowId = wt-dae4-91cd-676d & scrnCompId = 62 HTTP / 1.1

Hier ist die Anfrage: web_submit_form ("ca", "Snapshot = t6.inf", ITEMDATA, EXTRARES, "Url = Transaktions- / Transport- / Aktionsereignis / ShipmentListActionEvents.js"), "Referer = https: // " -X.lb.com/manh/index.html ", ENDITEM," Url = / services / rest / lps / ComponentService / config / 305? _Dc = 1457259096313 & windowId = wt-dae4-91cd-676d & scrnCompId = 62 ", "Referer = https: // -qa.lb.com/manh/index.html", ENDITEM,
LAST);

0

1 Antwort auf die Frage

0
James Pulley

Correlate your source for the Window ID.

There are easier ways of handling this issue however. When you run in HTML mode, versus URL mode, the page is brought into memory and parsed for the resources to request downstream. You can effectively comment out the extra resources noted in the script (EXTRARES) and run your HTML mode script, have the virtual user parse the page and load the extra resources based upon both the browser emulation settings as well as the cache headers for the resources.

Don't take my word for it. Comment out the extra resources and then run with full logs for a couple of pages. You should see in your logs the evidence of the page being parsed and the resource files being requested as needed.

Verwandte Probleme