Anyone knows how to add chromedriver.exe to path - selenium-chromedriver

i am getting an error called selenium.common.exceptions.WebDriverException: Message: 'chromedriver.exe' executable needs to be in PATH. Please see https://sites.google.com/a/chromium.org/chromedriver/home,
i tried to automate google chrome but it says it needs to be in path can someone say how to add to path

Are you running Java?
In Java you can use this
System.setProperty("webdriver.chrome.driver", D:\\chromedriver_win32\\chromedriver.exe");
Replace path with your ChromeDriver Path

Related

Trouble installing PHP Code Sniffer

I'm attempting to install PHP Code Sniffer for PhpStorm, but have been unable to get it to work. I've been following the steps here: https://confluence.jetbrains.com/display/PhpStorm/PHP+Code+Sniffer+in+PhpStorm
I added PHP Code Sniffer as a Composer dependency, and it now appears in the project directory. I then went to the code sniffer settings page, where I entered the path to the PHPCS.bat file. When I click Validate, I get an error message saying "Can not run PHP Code Sniffer".
Have I missed a step or is there a log somewhere with more information on what is not working?
I solved the same problem by editing the phpcs.bat file and replacing the paths:
PHPBIN=#php_bin#
with
PHPBIN=path\to\php.exe
and
"%PHPBIN%" "#bin_dir#\phpcs" %*
with
"%PHPBIN%" "path\to\phpcs" %*
I had the same issue, I solve it adding the php path to the PATH environment variables on windows. Because when it runs the scripts needs to run php and if it not present on the global path of windows will fail.

How do I set up the component build to build chromium?

I am trying to build Chromium and am stuck on the step that involves building the component build.
I have tried the instructions at http://www.chromium.org/developers/how-tos/component-build but I am having difficulty getting them to work.
I type in "python build\gyp_chromium -D"component=shared_library" into a command prompt and get:
C:\Users\username>python build\gyp_chromium -D"compoment=shared_library"
C:\depot_tools\python_bin\python.exe: can't open file 'build\gyp_chromium': [Err
no 2] No such file or directory
What am I doing wrong?
Thanks!
The file name is gyp_chromium.py. You forgot the extension

JSLint with Sublime text 2 - The system cannot find the file specified

I have installed JSlint properly but when I tried to run it I got below error:
[Error 2] The system cannot find the file specified
[cmd: [u'/usr/local/bin/node', u'/usr/local/bin/jslint', u'--sloppy', u'--indent', u'2', u'--node', u'--nomen', u'--vars', u'--plusplus', u'--stupid', u'']]
[dir: C:\Users\agrawal_d\AppData\Roaming\Sublime Text 2\Packages]
[path: C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\TortoiseSVN\bin;c:\Python27;C:\Program Files\nodejs\;C:\Users\agrawal_d\AppData\Roaming\npm]
[Finished]
Not understanding why it's showing this, can anyone please give me the solution
I got this problem as well and I hacked the file JSLint.sublime-build under installed JSLint package directory by replacing /usr/local/bin/node by the path to my node and it works.
Seems you're installing sublime text under windows platform. maybe you need to find the path to your node installation (e.g., C:\Program Files\nodejs\bin\node) and make sure the JSLint package can find it.
jslint most likely must be separately installed on your computer using Node and NPM package manager
Please follow the plug-in installation instructions on the plug-in README.
Here is a guide with some pictures
http://opensourcehacker.com/2012/04/12/jslint-integration-for-sublime-text-2/
It seems weird but in my case the solution is different. I was getting following error:
FileNotFoundError: [WinError 3] The system cannot find the path specified: 'c:\\users\\arvind~1\\appdata\\local\\temp\\SublimeLinter3-arvind\\app.js'
I checked the c:\\users\\arvind~1\\appdata\\local\\temp\\ folder and found that it had not SublimeLinter3-arvind folder. I created this folder manually and JSHint it started working..

How do I use html5bolierplate build script?

Okay, so.
I've installed Ant.
Downloaded the build script. Extracted to Ant installation location.
When I run the 'runbuildscript' a cmd interface opens for around a second, and stops.
If I navigate to the location of files through CMD, then do ant minify it doesn't work.
I then thought to place and extract the build script in the location of the files.
Upon doing so, an error came -
BUILD FAILED
E:\NamanyayG\wamp\www\namanyayg\build.xml:150: The following error occurred whil
e executing this line:
E:\NamanyayG\wamp\www\namanyayg\build.xml:416: E:\NamanyayG\wamp\www\${dir.source} does not exist.
Please help me out, I'm thoroughly confused.
Build script expects some external process (in this case you) to set dir.source property.
The most sure way to set it is to define it on ant command line, e.g.
ant -Ddir.source=/path/to/dir.source

Parsed Console Output Error in Hudson

im running Hudson continuous integration for db unit.
when i run the job the console output is displaying the SUCCESS, but then why do the Parsed Console Output keep returning this error:
ERROR:Failed to parse console log :
log-parser plugin ERROR: Cannot parse log: Can't read parsing rules file:
i already installed the parse-log plugin & i already restarted the Hudson..
i installed the plugin using remote PC
any help and suggestion is appreciated. Thanks!
1) Place the Parser Rule File in the JENKINS_HOME location.
2) Configure that log parser console output in the Global COnfiguration settings and Name it.
3) Add this option in the Post Build Actions and Select the Name
ok silly me..
i forgot to configure the global configuration in hudson that link to the parser rule file..
problem solved.
I'm posting this in case anyone else has a specific case of this problem. This issue started when upgrading from 1.509.2 to 1.554.3... I had the parsing rules file in the win\system folder which was a known issue when running Jenkins as a service. Well I guess they fixed it by this version. I moved the parsing rules back into Jenkins Home folder and it worked fine again.