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

Automatic Browser Restart (when frozen/hung) feature broken from v1.0.0 onwards #3781

Closed
sijosyn opened this issue May 9, 2019 · 2 comments
Assignees
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. TYPE: bug The described behavior is considered as wrong (bug).
Milestone

Comments

@sijosyn
Copy link

sijosyn commented May 9, 2019

What is your Test Scenario?

I wonder what happened to this feature this was first introduced in v0.23.0 - Browsers are Automatically Restarted When They Stop Responding. This is an excellent feature and was working fine up until v0.23.3. When TestCafe v1.0.0 came out, this feature stopped working (even happens in v1.1.4). TestCafe won't restart the browser when it goes into hung/frozen state (Browser instances are open but no actions happen inside the browser window). I don't have 100% reproducible test to provide to reproduce this issue as TestCafe freezes for some unknown reasons. When we run in tests in Bamboo CI server, our jobs are getting stuck because TestCafe goes into hung state and we have to manually kill the job & shutdown all open browsers (see screenshot).

I would love to have this feature working back again. Can you guys take a look at the feature again and see why/where it might be broken?

What is the Current behavior?

When TestCafe encounters some strange issue, TestCafe freezes and stays frozen/hung state forever. It won't quit & restart the browsers and attempt to run the tests again.

What is the Expected behavior?

If a browser stops responding while it executes tests, TestCafe restarts the browser and reruns the current test in a new browser instance. If the same problem occurs with this test two more times, the test run finishes and an error is thrown.

What is your web application and your TestCafe test code?

Your website URL (or attach your complete example):

Your complete test code (or attach your test files):
 
Your complete test report:

Screenshots:

f502bc

Steps to Reproduce:

No exact 100% reproducible test script to provide to reproduce this issue.

Your Environment details:

  • testcafe version: Happens in v1.0.0, v1.1.0, v1.1.3 & latest v1.1.4 . Works fine in v0.23.3
  • node.js version: v8.11.1
  • command-line arguments:
  • browser name and version: Chrome 74
  • platform and version: macOS 10.14
  • other:
@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label May 9, 2019
@AlexKamaev AlexKamaev self-assigned this May 13, 2019
@AlexKamaev
Copy link
Contributor

I was able to reproduce the problem. We'll research it and keep you updated shortly.

@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label May 13, 2019
@AlexKamaev AlexKamaev added the TYPE: bug The described behavior is considered as wrong (bug). label May 13, 2019
@AlexKamaev AlexKamaev added this to the Sprint #33 milestone May 13, 2019
AlexKamaev added a commit to AlexKamaev/testcafe that referenced this issue May 20, 2019
AlexKamaev added a commit to AlexKamaev/testcafe that referenced this issue May 21, 2019
@lock
Copy link

lock bot commented Jun 2, 2019

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.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Jun 2, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 2, 2019
kirovboris pushed a commit to kirovboris/testcafe-phoenix that referenced this issue Dec 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

2 participants