Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chrome does not close automatically after tests have been executed #1

Open
asciidisco opened this issue Aug 22, 2013 · 3 comments
Open
Assignees
Labels

Comments

@asciidisco
Copy link
Member

After updating to chromedriver 2, the browser doesn't close automatically, after the test run has been finished.

Maybe we need to add smth. like we did in dalek-browser-ie, saving the newly created process & killing it on our own.

@ghost ghost assigned asciidisco Aug 22, 2013
@asciidisco
Copy link
Member Author

Issue resolved.
The browser plugin now keeps track of the already running chrome processes & closes the ones that the driver opened after the tests have been executed.

@omarlopesino
Copy link

I have that problem running the tests on chrome now. I'm using chrome remotely in Windows 7 from kubuntu.

@asciidisco
Copy link
Member Author

@OmarMoper Yep, that is a windows related issue.
Most probably the same thing that happend here: dalekjs/dalek-browser-ie#11

Do you want to give porting the changes from the IE module, to this one, a try?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants