What is your Test Scenario?

Running some test on browserstack when the allowed parallel tests have reached it upper limit.

What is the Current behavior?

Browser is not closed when trying to kill a test that is in the queue.

What is the Expected behavior?

Browser should be closed regardless whether the test is running or in a queue.

What is your web application and your TestCafe test code?

Any simple test should be fine.

Steps to Reproduce:

1. Prepare some tests written in testcafe, link the dependency of testcafe-browser-provider-browserstack to this updated repo.
2. Prepare a test account in browserstack
3. Run some tests and make sure it browserstack reaches its subscription limitation.
4. Start a new test, for example

$ yarn testcafe browserstack:ie my-test.js
yarn run v1.10.1
$ /Users/daniel.han/git/.../node_modules/.bin/testcafe browserstack:ie tests/functional/my-test.js
⠙
Daniel Han >>>>>>>>> init
⠴
Daniel Han >>>>>>>>> isValidBrowserName ie
⠦
Daniel Han >>>>>>>>> openBrowser y_KXdxg http://10.3.222.225:56298/browser/connect/y_KXdxg ie

At this monent the new test will be saved into a queue of browserstack (due to a bug in browserstack the size of queue can be infinite, but don't bother about that for now)

5. Kill the test by killall node
   Normally when the you kill a running job, closeBrowser will be called. But in this case, when the job is in the queue, it will not be called. As a result the test will be hanging on browserstack for 30 minutes until the whole session times out.

For more information about the debugging code please check out here:
https://github.com/hex0cter/testcafe-browser-provider-browserstack