Highlighted
Absent Member.
Absent Member.
92 views

Context of GUI: Web/HTTP vs. Click & Script ...

With the common web/http protocols we don’t generally have to worry much about where we leave the GUI at the bottom of our Action() function, since we’re dealing with data streams, just requests and responses, the scripts will generally work fine at the top of the loop in the action() function. In contrast to this, think of WR or QTP, if you have a loop, you need to make sure you leave the GUI in the same state at the bottom of the loop as you did at the top of the loop, right?

So here’s my question. When we use the various Click & Script protocols, do we need to treat the navigation more like WR/QTP? I’m guessing we do?

Thanks very much in advance!
Chris
0 Likes
2 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Context of GUI: Web/HTTP vs. Click & Script ...

What you said is exactly correct

Regards,
Madan
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Context of GUI: Web/HTTP vs. Click & Script ...

Thanks, Madan! 😉
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.