Posted: April 21st, 2008 | Author: TnT Admin | Filed under: Concepts | Tags: HTTP/HTML, Script, Socket, WinINet | No Comments »
The Windows Internet (WinInet) application programming interface (API) enables applications to interact with Gopher, FTP, and HTTP protocols to access Internet resources. As standards evolve, these functions handle the changes in underlying protocols, enabling them to maintain consistent behavior. If you want detailed information on the APIs of WinInet, you can find them in the article, “About WinINet” at Microsoft. Whereas for Socket Level, it is a proprietary API that Mercury/HP LoadRunner implements. Read the rest of this entry »
Posted: April 21st, 2008 | Author: TnT Admin | Filed under: How-Tos | Tags: HTTP/HTML, Scripting | No Comments »
There are situations where recording application using protocol Web (HTTP/HTML) encounters problem such as (1) not recording events, (2) not launching or (3) crashing. The context may deviate however the below list aims to provide a quick-and-dirty resolution to the problems. Obviously, the quick-and-dirty may work/not work in different environment and situations, however it will help you scope down the problem in a sequential and logical manner. Read the rest of this entry »
Posted: April 21st, 2008 | Author: TnT Admin | Filed under: How-Tos | Tags: HTTP/HTML, LoadRunner, MMS, Protocols | 5 Comments »
Have you ever wanted a combination of two separate protocols that were unavailable in the list of multi-protocol? For example, part of the web application has streaming video component and the activities to be recorded requires you to login, conduct some verification before you have the video link for the user to click. If you need to test the entire flow, you may want to have Media Player (MMS) with Web (HTTP/HTML) combined together to emulate the activities. Read the rest of this entry »