Chome doesn't close with command+q on Mac

[Nuarat]

Are you requesting a feature or reporting a bug?

Bug

What is the current behavior?

TestCafe doesn't close Chrome when interrupted with command+q

What is the expected behavior?

TestCafe should close chrome

How would you reproduce the current behavior (if this is a bug)?

On MacOS, when tests are running in Chrome, press command+q, in the console

Provide the test code and the tested page URL (if applicable)

Tested page URL:

Test code

Specify your

• operating system: MacOS
• testcafe version: 0.18.5
• node.js version: 8.9.3 LTS (?)

[robhrt7]

Experiencing the same issue since few months.

MacOS version 10.13.2
Testcafe 0.18.6
Chrome 63.0.3239.84

[robhrt7]

Same happens with Firefox, multiple instances hanging after few test runs, but tests shown to be successfully completed in console.

[AndreyBelym]

Hi @operatino! Unfortunately, it's not possible to handle Command + Q gracefully in a command line app. This key combination sends close command to the Terminal app, and it will terminate its children command-line process unconditionally if you agree to close running processes. It means TestCafe has no possibility to detect termination and sends close command to browsers.

[lock]

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.