Running JUnit via Mavin, chromedriver tests randomly end with two DELETE session commands about chromedriver HOT 7 CLOSED

In your log, it looks like the failing test is closing the window and then 
calling quit. Closing the window automatically quits if it is the last window. 
I don't think this is a ChromeDriver server issue, since ChromeDriver is 
receiving the quit twice. It looks like either the WebDriver client or your 
test case has some race leading to the double quit.

I tried setting up a few parallel tests with maven, but wasn't able to 
reproduce the problem. However, I may not have setup my project correctly for 
parallel test execution. It appeared the tests were only running one at a time, 
although the stdout had:
-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Concurrency config is parallel='methods', perCoreThreadCount=true, 
threadCount=6, useUnlimitedThreads=false

I've never used Maven before. Is this correct?

[deleted comment]

Good call! My test framework overrides the finished() method of 
org.junit.rules.TestWatcher. The implementation invokes driver.close() followed 
by driver.quit()

Removing the call to driver.close() should resolve this issue.

Hello I am facing this issue


Error 
 The path to the chromedriver executable must be set by the webdriver.chrome.driver system property; for more information

If i have to run it from cmd using mvn install , who i need to define the 
dependencies of chrome driver.As currently i am using  

        <dependency>
            <groupId>org.seleniumhq.selenium</groupId>
            <artifactId>selenium-java</artifactId>
            <scope>jar</scope>
     <version>2.20</version>

and Running the in code as 

WebDriver driver = new ChromeDriver();
driver.get("http://www.google.com");

241.aditi, your issue is different.

See http://code.google.com/p/chromedriver/wiki/GettingStarted