I recently started contributing to dev.to's GitHub repository by refactoring some .js files to meet the eslint specs. Some of the files that need to be refactored require multiple other ones to be refactored too at the same time in order to not break certain functionality.
In order to check for that I have been trying to setup the Acceptance testing as specified in the docs + with some online help to check whether all functionality remains as is or not. But I have been hitting various hurdles throughout where either the chrome binary wouldn't be found, post that after installation it posted Invalid Session id
or sometimes it would work totally. It's a mystery for me currently.
Any help / pointer in the right direction would be much appreciated :D. Willing to provide any details required for the same!
Top comments (4)
So I managed to get tackle the chrome issue by using WSL's feature to access Windows binaries from Linux and calling the chrome installed to my windows. But the problem I am getting stuck at now is that it isn't able to perform any actions. It opens blank chrome console windows and just sits until it timesout with:
Also a
debug.log
file is generated in the repo with content:Seems to be a firewall issue? But disabling windows firewall doesn't allow it through too.
Hi did you end up fixing this issue?
Hey, the issues I was facing got resolved once WSL2 came out. With WSL2, it became possible to install chrome directly to my Linux distro without any problems. I followed the following steps for Ubuntu 18.04 with bash:
If you get an error while running
dpkg
, runsudo apt --fix-broken install
after which run thedpkg
command again. You can run the following command to test your install:thanks , it works. this what I been searching for