Automated Web Test

This is a follow up of the previous posting about LoadRunner and Flex applications. The issue with LoadRunner interfereing with the Flex application during recording was solved. It had been an issue with the recording engine.

Two solutions were offered by HP and the first one worked fine.

Changing the registry key HKEY_CURRENT_USER\Software\Mercury Interactive\LoadRunner\Protocols\HTTP\Analyzer in the registry and set AddNoCacheHeaderToHtml to 0.

The second solution offerred was to go under recording options –> Network –> Port Mapping –> set Capture Level to “WinINet level data”.

If this information was useful to you please leave a message.

LoadRunner 9.1’s Flex protocol includes both AMF3 and Http protocols in its options. For testing applications using Flex and AMF3 protocols, these options need to be explicitly added in the recording options. To do this:

1. Click on options in the recording window.

2. Check the AMF and Http protocols in the Recording Options window under the subhead - Protocols.

3. Check the “Try to encode externizable object” option in the “Code Generation” Subhead of Recording Options window.

Recording after these options are checked would give more readable code as XML rather than Binary.