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

TestCafe fails to restart browser if it became unresponsive. Broken in v1.0.0 onwards. #1953

Closed
sijosyn opened this issue Mar 5, 2019 · 4 comments
Assignees
Labels
AREA: client STATE: Auto-locked Issues that were automatically locked by the Lock bot SYSTEM: iframe processing TYPE: bug
Milestone

Comments

@sijosyn
Copy link

sijosyn commented Mar 5, 2019

What is your Test Scenario?

I'm reporting 2 issues in the same ticket.

Issue 1 - TestCafe fails to restart browser if it became unresponsive. This feature is broken starting from v1.0.0 (& v1.1.0) but works fine in v0.23.3 (#1815) . TestCafe is supposed to do the following but it stays frozen and won't restart the browser. See test code provided below to demonstrate this issue.

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.

Issue 2 - TestCafe fails to fully load the provided test page URL and stays in hung state and won't even throw a failure error. Please check why it stays in frozen state.

What is the Current behavior?

See above.

What is the Expected behavior?

For issue 1 - TestCafe should restart browser if it became unresponsive.
For issue 2 - TestCafe should load the page elements and should not freeze and should complete the test run.

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):
import { Selector } from 'testcafe';

fixture `Episode fixture`
	.page `https://aperture.synacor.net/video/details/category/episode/id/290541212/title/I'd%20Rather%20Be%20Crafting/`;

test('Test', async t => {
	await t.expect(Selector('.video_details-hero_title').innerText).eql(`1. I'd Rather Be Crafting`);
});
Your complete test report:

Screenshots:

Steps to Reproduce:

Please run the provided test code.

Your Environment details:

  • testcafe version: v1.0.0 & v1.1.0
  • node.js version: v8.11.1
  • command-line arguments: testcafe chrome test.js
  • browser name and version: Chrome 72
  • platform and version: macOS 10.14
  • other:
@miherlosev miherlosev self-assigned this Mar 5, 2019
@miherlosev
Copy link
Contributor

miherlosev commented Mar 5, 2019

Hi @sijosyn

Thank you for the detailed description. I've reproduced the problem.

For team: We should to encode the referrer property.
image

@sijosyn
Copy link
Author

sijosyn commented Mar 29, 2019

@miherlosev / @AndreyBelym - Can you please prioritize this issue and fix it asap? This is blocking bunch of our tests as TestCafe hangs/freezes when it runs to issue. Thanks.

@AlexKamaev
Copy link
Contributor

AlexKamaev commented Apr 5, 2019

@sijosyn
Sorry for delayed response. I've added this ticket to the current sprint, so we will try to fix it soon

@lock
Copy link

lock bot commented Apr 18, 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 Issues that were automatically locked by the Lock bot label Apr 18, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Apr 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
AREA: client STATE: Auto-locked Issues that were automatically locked by the Lock bot SYSTEM: iframe processing TYPE: bug
Projects
None yet
Development

No branches or pull requests

5 participants