I am trying to record with Chrome in LoadRunner for the first time (having to record a mobile app through an emulator that only works in Chrome), but when recording with Web (HTTP/HTML) protocol in Chrome I only get empty actions, no events are recorded (tried with several "standard" web pages).
LoadRunner opens Chrome fine, I click a few links and then stop recording, but script actions remain empty. Using HTML-style recoring.
Setup:
Windows 7 64 bit SP1
Loadrunner VuGen v11.52
Chrome v27.0
I have colleagues that manage to record fine with similar (if not exact same) setup. Has anyone faced the same issue?
You must close all Chrome windows before starting recording and use only the window that VuGen opens to record. Also make sure no chrome processes running before recording.
Why not record the actual device with vugen instead of an emulator?
Keep in mind you are trying to use a 32 bit application to record a 64 bit application. I would even go so far as to recommend that you look at using the proxy model recording as an HTTP proxy for the "old recording engine."
Related
We Azure DevOps Server 2020 on-prem. And I noticed that I cannot open more than just a few Azure DevOps builds in different Chrome tabs concurrently. Namely, here is what I am doing:
Navigate to an Azure DevOps build and wait until all the details are loaded.
Repeat step (1) for another build
What I have noticed is that after 5-1 tabs (sometimes I am "blessed" with 5 fully loaded tabs and sometimes I cannot have more than 1) no new tabs are able to load the build details. I am using builds as an example, could be PRs or other screens.
At first I thought we have some concurrency limit on the server, but we do not. Neither IIS nor the Sql Server serving the requests have any concurrency limit defined. But then, I have discovered an even weirder thing - this concurrency limit exists in Chrome and Edge, but not IE!
I do not want to make IE my default browser, I would prefer keeping Chrome. But this drives me crazy.
My current theory is that it has to with signalr. Azure DevOps frondend uses some kind of signalr implementation. Maybe Chrome and Edge are too "advanced" to handle it correctly? Or maybe IE does not handle it at all and so Azure DevOps server fallsback to something IE supports and as a result no throttling is experienced?
I am pretty lost here and have no idea how to troubleshoot it further. Any ideas?
EDIT 1
Initial inspection of the URLs visited from chrome vs IE shows a difference in signalr urls:
IE: transport=webSockets
Chrome: transport=serverSentEvents
Does it make sense to anyone? Could this difference explain why Chrome is unable to open more then 1-5 (1 sometimes happens in the evenings) tabs serving Azure DevOps Server 2020 web pages?
EDIT 2
Right at this moment the limit is 6. I have 6 tabs open on the same exact build, 7th is hanging. The Network tab in the browser shows it is being stuck on the very first server side request to http://theserver:8080/tfs/DefaultCollection/SharpTop/_build/results?buildId=1184073&view=logs&j=ca395085-040a-526b-2ce8-bdc85f692774. No response at all. But if I close any of the other 6 tabs, it would load immediately.
EDIT 3
Posted on the MSFT Dev Community site - https://developercommunity.visualstudio.com/t/unable-to-load-more-then-6-sometimes-less-tabs-of/1466416
Hi it could be some product issues around the supported browsers with policy/configuration on how http/https would handled, suggest you open up issue in the Azure DevOps Developer Community , and MS PG/support team can dive in to feedback you.
the similar has opened Azure DevOps Server not loading properly that close to your descriptions here.
I want to have chrome in kiosk mode to show my website. The problem is though, the website is offline around 10% of the time.
I created the .bat script that pings the website and shows another one if it fails to ping.
The problem is the website changes once per week and I have this script on 60 kiosks, so updating automatically would be problematic.
What would be the easiest way to update those kiosks having only chrome and windows batch? I cannot install git, python etc on them.
I'm trying to record a script with LoadRunner but nothing happens...
I'll try to be more specific: I create a new web-based script (Web - HTTP/HTML) because I want to record actions taken into IE.
I start doing things in IE and then stop the recording.
What I expect is to find into "Action" the code that describes what I've just done in IE but nothing appears: "Action"contains only the return.
Any idea about what could be the issue?!
EDIT: I'm not recording any HTTPS action...
Have you engaged in any activity in IE which connects to a server across the HTTP protocol, submitting requests and pulling responses? if not, then you should not expect to see anything recorded.
There are also all sorts of permutations of 64 bit IE, of specific release numbers, versus your 32 bit recording engine of LoadRunner and specific release numbers, plus your credentials and any conflicts from antagonistic antivirus that could come into play.
The sample applications are your control set, such as the sample flights reservation system. If you cannot record against that site with your version of LoadRunner then you have a conflict in one of the following
Failed Installation
Wrong Credentials
Conflicting Antivirus (disable for testing)
version conflicts (see requirements for your version of LoadRunner)
64 bit IE and 32 bit VUGEN (see proxy model for recording)
You may try local proxy recording.
What versions of chrome are compatible with loadrunner 11.52 on windows?
I saw a post that said version 26 was supported, but Im looking to record using chrome version 13 on windows 7
NB: Browser version is mandated by the project.
NNB: Assume playback is browser agnostic - as the commands generated will send the raw HTTP(S) requests to the target server, without any UI
All versions when using the proxy recording model.
I just recorded again , and quit before I got the site up (so recorded for about 4 minutes with an empty chrome screen and a spinning timer) to see what Loadrunner recorded - I got web_url, web_add_cookie & web_custom_request for google safebrowsing & related api - ...
Unless you work for Google or have their expressed written permission then you do not use automated tools against their site. This is why the sample applications exist. Or, you may download and install onto a server you own, control, manage, ... any of the thousands of open source applications which are available on the market.
Pointing an automated tool at a site you don't own, manage or control is no different than driving down the street and shooting at parked cars, homes and signs just because they are there and you can. Pointing a performance testing tool at the same is akin to pointing a piece of field artillery at someone's home. This is something you do not engage in as a performance test professional.
Any ideas on how to get memory usage, Javascript errors, etc. from Chrome running on Google TV?
I have a page that is getting the "Aw, snap!" error when viewed in the Chrome browser on Google TV (Logitech). The page is fairly simple, but it does load a bunch of photos, though only up to 7 at a time (the photos are loaded using JavaScript). The photos are 640x480 and ~500KB each. They are stacked and the top one fades out (using jQuery) until all are gone then a new batch is loaded.
It only crashes on Google TV (it runs fine on Windows 7) and it takes a while before it crashes (I can get it down to about 10-20 minutes before it crashes by turning on a "fast mode" on our page).
Unfortunately I can't figure out how to get any information that might help me debug it. It would be cool to be able to get Chrome's developer tools on the Google TV device.
Currently there is no way to pull debug information from Chrome on Google TV. The Logitech Review is rather limited in it's RAM and you may be encountering an issue there (I don't know how big these images are). It is also possible that you have a memory leak in your javascript code. This might be hidden on other systems running a browser as there would be more memory to buffer you from seeing the error.
My advice would be to create a virtual machine (VirtualBox is free and runs on Windows) - create a VM with limited memory (256Mb Ram for instance) and install Ubuntu or some other flavor of linux that can run Chrome. Then run your app in the VM and see what happens.
Failing that you could always try loading the imaged with static image tags and see if it is the images that are causing the crash. If it's not the images then I would say look at your JS code closely and perhaps run it through JSLint (http://www.jslint.com/)