I have side by side chrome installs for testing:
version 35
version 13
To launch version 13 I have a separate chrome application directory and pass in some command line switches e.g.:
--user-data-dir="C:\UserData" --chrome-version=13.0.782.218
This works fine, on the desktop I just create a shortcut to the exe and tag on the switches.
How do I do that when I record in Loadrunner?
I can browse to the exe from the "start recording" dialog, but I can't add the switches.
Using the desktop shortcut with the switches doesn't work.
Any ideas?
If your website does not generate chrome specific code then just use any browser for recording
You can always record in proxy mode any HTTP based communication you wish, whether on machine or not.
Related
I have 2 chrome profiles. My aim is to control these 2 windows using puppeteer. So first, I have to open these profile windows via command line, specifying the debugging ports.
command 1: google-chrome --remote-debugging-port=9222 --profile-directory="Default"
command 2: google-chrome --remote-debugging-port=9223 --profile-directory="Profile 1"
When 1st command is executed, it opens a chrome window with the profile I mentioned. And I also get a WS URL for that browser. So I can use that in puppeteer.
Problem is while running second command. It also opens the profile, but no URL. It says "Opening in existing browser session".
I want to open more profiles and control them with puppeteer. Please help.
Since last week (March 25th), I am unable debug using node inspect. I have been using node 8.11.4, and have not updated node version.
After I run node --inspect filename.js I was able to go to chrome://inspect/#devices and click on Open dedicated DevTools for Node, and this used to attach the debugger and load the file.
Now it doesn't show anything in the inspect window.
However, it does show file in Remote Target, but only those files are shown that I had opened previously. I still don't see any files in Sidebar. And Reveal in Sidebar does not show me the current file.
I am using Chrome Version 73.0.3683.86.
This is a bug in chrome:
https://bugs.chromium.org/p/chromium/issues/detail?id=941608#c15
The fix is due for release in the next version (22nd April). In the meantime, either use NiM (chrome extension) or download the google chrome beta. I can confirm that it is working again using chrome beta.
https://www.google.com/chrome/beta/
I keep getting this browser (chrome) notification saying
Adobe Flash Player was blocked because it is out of date. Update, Run This Time
If I click run this time it allows me to run any flash content on current page but same notification on new page. If however, I click update plugin it takes me to this Chrome support page. I follow instructions and go to chrome://plugins which give me a url under Adobe Flash Player which is following Download Critical Security Update and as you see this again links me to the Google support page with instructions on how to update and that I've already been on.
I encountered the same issue with Chrome on my Linux system.
Here is my solution for Linux system:
Install chrome 55+, if you have an older version.
Download flash player,
url: http://get.adobe.com/flashplayer/
step 1 - os
choose "linux 64 bit",
step 2 - version
choose "FP xx for linux 64-bit (.tar.gz) - PPAPI",
Download,
Uncompress,
Copy files in the directory into ~/.config/google-chrome/PepperFlash/,
Make it executable via: chmod +x libpepflashplayer.so
Append parameter to chrome's start command,
Where is the command:
(1) for icon,
right click icon -> properties, there is "command" input,
(2) for shortcut,
config the shortcut,
The parameter to append is:
--ppapi-flash-path=/home/eric/.config/google-chrome/PepperFlash/libpepflashplayer.so
e.g.
/usr/bin/google-chrome-stable %U --ppapi-flash-path=/home/eric/.config/google-chrome/PepperFlash/libpepflashplayer.so
Restart chrome,
Now the flash should work.
I assume you have solved your issue by now, but for the benefit of others: Flash is now provided as a so-called component and updated separately from the main Chrome application. I would therefore suggest first checking chrome://components and manually check for an update there.
By the way, the same is true for the Widevine DRM component, which if not up-to-date may stop Netflix, etc. from running.
Is it possible to launch a Chrome app without having the Chrome Browser appear?
In other words can the browser run in the background and launch a chrome application?
Yes, if the app creates its own window then just run it from the Chrome app launcher or make the shortcuts on desktop / startmenu / taskbar: open chrome://apps/ page (it can be opened from the new tab page), right-click the app, click Create shortcuts.
To run the app using command line use the app ID (to get it first create a shortcut as described above and simply copy the command line from the shortcut's parameters, or you can copy it from the webstore page of the app), here's a Windows command line using start which automatically finds the installed Chrome executable:
start chrome --app-id=pelimflkpjiicnajdjcmekpioacmahkh
P.S. The app must be installed in the browser.
I know how to enable chrome's crash reporting interactively:
Menu > Settings > Show advanced settings > Tick "Automatically send usage statistics and crash reports to Google"
However, I'm using chrome in an automated testing setup where we set a new --user-data-dir for each run (so there are no persisted settings, we just get the defaults). Chrome is crashing occasionally (running our javascript/html application) and I would like to be able to report these crashes.
I thought I could add --enable-crash-reporter (according to the List of Chromium Command Line Switches), but that doesn't seem to do anything. (We already pass --enable-logging and a couple other flags on the command line.)
I have a test that triggered an "Aw, Snap":
But if I download the user-data-dir for that run and and point chrome at it, and then visit chrome://crashes, it says crash dumps are not enabled.
(The chrome_debug.log does not say anything about the Aw-Snap either.)
We're running chrome under Xvfb on Debian. We're driving chrome via the direct webdriver (from Protractor).
According to the "crashpad with content shell" docs, the steps for using crashpad with content shell (a stripped down version of Chrome):
Create some directory for your crash dumps to go to (the docs suggest tmp/crashes on Linux and Mac, %TEMP%\crashes on Windows, and /data/local/tmp/crashes on Android)
Start Chrome with --enable-crash-reporter --crash-dumps-dir=<your_dump_dir> (looks like you got half of this)
So I'd try adding the --crash-dumps-dir flag.