So the funny moment.
I tested my app and ran tests on Karma + Jasmine before commit with Husky tool. Once Chrome got stuck and after reboot system Chrome always opens as a new Karma window in incognito mode. The Chrome icon is renamed too.
I tried to reinstall Chrome but issue still exists. I have:
Distributor ID: Ubuntu
Description: Ubuntu 16.04.5 LTS
Release: 16.04
Codename: xenial
So I can I revert changes and get back my lovely Chrome?
Ok, so Karma has configurations in ~/.local/share/applicaitons. It lock the Chrome and creates a karma-<random-numbers> test kit in tmp folder.
To fix it
cd ~/.local/share/applicaitons
rm google-chrome.desktop
Related
I am trying to run automated tests on a repository forked from here. I haven't really worked with yarn or mocha before (or chromedriver) so I'm going off of what the instructions are saying.
I've set up Ubuntu 18.04 in wsl2 and installed google-chrome-stable and chromedriver both at version 99.0.4844.51 in /usr/bin/. I have yarn start running in one terminal and when I try actually run yarn test it gives me:
SessionNotCreatedError: session not created: This version of ChromeDriver only supports Chrome version 94
Current browser version is 99.0.4844.51 with binary path /usr/bin/google-chrome-stable
I've tried upgrading chromedriver from here to version 100.0.4896.20 but it gives me the same error saying it only supports Chrome version 94. I'm having a hard time trying to find Google version 94 for linux, and I'll be happy either way, either upgrading the chromedriver or downgrading chrome.
I am running tests in Jenkins and the tests are running on outdated Chrome 71 and I want to update the chrome it is using. I've tried updating my package.json to current TestCafe but it is still running 71. when I run node_modules/.bin/testcafe --version it just lists firefox, chrome. It seems that since the chrome is in node_modules I should be able to update to latest but I haven't found anything online to show how to do so.
Running locally on my machine chrome is v91. I thought doing an 'npm i' locally and pushing that branch would update but it was not successful.
Jenkins output:
npm i
node_modules/.bin/testcafe --version
1.15.0
node_modules/.bin/testcafe -e chrome:headless auth-subscriber-signs-in-validates-homepage.js
Running tests in: Chrome 71.0.3578.98 / Linux 0.0
TestCafe doesn't upgrade or downgrade browsers. It just searches the installed browsers and runs tests in them. You need to inspect the Jenkins job and found the way how browsers are installed for it.
I utilize Google Chrome Canary for development work.
System:
OS: macOS Big Sur 11.2.3
Processor: i7
Since Canary has a nightly build, I am regularly running Update Chrome button in the browser, but not every day. Yesterday, this update caused Canary to crash. I tried the following:
Restarting Canary
Downloading and re-installing the Canary build
Restarting my computer
None worked. Today, I simply re-downloaded the nightly build, and voila all was working again.
(Working Build: Version 92.0.4476.0 (Official Build) canary (x86_64))
On the above link, they fully warn ye who enter here:
Get on the bleeding edge of the web. Be warned: Canary can be unstable.
So I guess I'll treat this, my first question, as practice if there really is no good answer:
Is there anywhere safe on the web to download and run a previous version of the Canary build in these situations? Otherwise I might just have to save my last stable download locally and have that as a fall-back.
You could find and backup the last build of your canary in these default folder:
For macOS:
~/Library/Application Support/Google/Chrome Canary/
For windows 10:
\Users\%USERNAME%\AppData\Local\Google\Chrome SxS\Application
I'm not sure if you could find the previous build in there.
I am trying to run my Cucumber tests headlessly with Chrome on Ubuntu 14.04 (EC2 instance so no GUI). So far my setup allows this, as the below screenshot shows:
I have an issue when I come to a page with flash on it:
I have restarted the EC2 instance and killed all chrome processes, still no joy.
To clarify, a test will start and chrome opens the page with flash on it and I get this message. If I then end the test and start it again I get the same problem. I guess this is not actually restarting chrome as it is a new instance each time?
So to run these tests I am using the headless gem here which acts as the interface to xvfb.
I have Google Chrome 57.0.2987.133 and have added libflashplayer.so to /opt/google/chrome/pluginsusing this https://askubuntu.com/questions/14629/how-do-i-enable-the-partner-repository
A few extras things I have tried include:
sudo apt-get install pepperflashplugin-nonfree
sudo update-pepperflashplugin-nonfree --install
Is there a way to get this to work so I can render flash based sites? Do I need to enable the flash plugin each time I open chrome? I'm hoping I've missed something obvious.
Update
I have tried setting the pepperflashpluginpath when creating the Chrome profile but this is still not working:
Capybara.register_driver :chrome do |app|
chrome_binary = '/usr/bin/google-chrome'
Selenium::WebDriver::Remote::Capabilities.chrome("chromeOptions" => { "binary" => chrome_binary, "args" => ["--ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"] })
Capybara::Selenium::Driver.new(app, :browser => :chrome, :desired_capabilities => capabilities)
end
Thanks
There were three key parts in getting this to work.
Install Chromium Browser
sudo apt-get install chromium-browser (at time this installed version 58)
The Chrome binary is now installed at
/usr/bin/chromium-browser
Install Flash plugin
https://askubuntu.com/questions/531672/how-to-install-flash-payer-in-ubuntu-14-04-lts
First go to /etc/apt/sources.list and uncomment the lines
deb http://archive.canonical.com/ubuntu trusty partner
deb-src http://archive.canonical.com/ubuntu trusty partner
Then run
sudo apt-get update
sudo apt-get install adobe-flashplugin
This installs the flash plugin at
/usr/lib/adobe-flashplugin/libflashplayer.so
Install Chrome Driver
Then run
sudo apt-get install chromium-chromedriver
sudo ln -s /usr/lib/chromium-browser/chromedriver /usr/bin/chromedriver
That's pretty much it, these were the steps that got me running this with Cucumber headless.
I have Google Chrome ver. 41.0.2272.118 and I decided to upgrade it.
I've dowloaded latest version of Google Chrome version 46.0.2490.86 :
Got:2 http://dl.google.com/linux/chrome/deb/ stable/main google-chrome-stable amd64 46.0.2490.86-1 [47,3 MB]
Then I check version from console:
maxim#maxim:/opt/google/chrome$ ./google-chrome -version
Google Chrome 46.0.2490.86
But when I run it
maxim#maxim:/opt/google/chrome$ ./google-chrome
and check About, it still show 41.0.2272.118
What did I do wrong?
I also had this similar problem on Linux Mint. I found the following solution to work.
Close all Chrome sessions
Update google-chrome using apt-get as you have done above
Move the config files from ~/.config/google-chrome to ~/.config/bkp_google-chrome
Start google-chrome and the new version should now be started.
Please note this will erase all your history, bookmarks etc