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 hangs on navigating to another page in electron #4701

Closed
psaikido opened this issue Jan 26, 2020 · 10 comments
Closed

Testcafe hangs on navigating to another page in electron #4701

psaikido opened this issue Jan 26, 2020 · 10 comments
Labels
FREQUENCY: level 1 STATE: Stale An outdated issue that will be automatically closed by the Stale bot. TYPE: bug The described behavior is considered as wrong (bug).
Milestone

Comments

@psaikido
Copy link

What is your Test Scenario?

An electron app. A page has an edit button which takes the user to a page to edit the values.

What is the Current behavior?

The test navigates to another page but thereafter just hangs.

What is the Expected behavior?

Should be able to test the new page.

What is your web application and your TestCafe test code?

https://bitbucket.org/psaikido/lyftrak/
https://bitbucket.org/psaikido/lyftrak/src/testcafe/testcafe/02-edit.js

Your complete test code (or attach your test files):
 
Your complete configuration file (if any):
{
    "mainWindowUrl": "./src/journalEntry.html",
    "appPath": "./"
}

Your complete test report:
There is no report because it's just hanging.
Screenshots:

Steps to Reproduce:

  1. Install lyftrak from bitbucket
  2. Execute npm test from its root dir on linux
  3. See the error...

Your Environment details:

  • testcafe version:
    v1.8.1

  • node.js version:
    v13.5.0

  • command-line arguments:

  • browser name and version:
    chrome Version 79.0.3945.117 (Official Build) (64-bit)

  • platform and version:
    linux mint 19.3

  • other:
    I wonder if the bug is to do with an interaction with npm package testcafe-browser-provider-electron.

@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Jan 26, 2020
@AndreyBelym
Copy link
Contributor

Thank you for your report. I was able to reproduce the issue. Likely it is an incompatibility between TestCafe and Electron, but we need some time for debugging.

@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label Jan 29, 2020
@AndreyBelym AndreyBelym added STATE: Need research STATE: Need response An issue that requires a response or attention from the team. and removed STATE: Need response An issue that requires a response or attention from the team. labels Jan 29, 2020
@psaikido
Copy link
Author

psaikido commented Jan 29, 2020 via email

@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Jan 29, 2020
@AlexSkorkin AlexSkorkin removed the STATE: Need response An issue that requires a response or attention from the team. label Jan 30, 2020
@trungutt
Copy link

Any update on this ?

@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Jan 10, 2021
@arubtsov
Copy link
Contributor

@trungutt, there are no updates yet. We will definitely post news once we have any.

@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label Jan 11, 2021
@AndreyBelym AndreyBelym added TYPE: bug The described behavior is considered as wrong (bug). and removed STATE: Need research labels Jan 18, 2021
@Dmitry-Ostashev Dmitry-Ostashev added this to the Planned milestone Apr 21, 2021
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this issue in the future. If it still affects you or you have any additional information regarding it, please leave a comment and we will keep it open.

@github-actions github-actions bot added the STATE: Stale An outdated issue that will be automatically closed by the Stale bot. label Apr 22, 2022
@github-actions
Copy link

github-actions bot commented May 2, 2022

We're closing this issue after a prolonged period of inactivity. If it still affects you, please add a comment to this issue with up-to-date information. Thank you.

@github-actions github-actions bot closed this as completed May 2, 2022
@2BC-Wasabi
Copy link

is there any fix? i'm facing the same problem now, i would assume that when i use loadurl on a browserwindow it creates new webcontents

@github-actions
Copy link

github-actions bot commented Aug 1, 2022

No updates yet. Once we get any results, we will post them in this thread.

@github-actions github-actions bot removed the STATE: No updates No updates are available at this point. label Aug 1, 2022
@github-actions github-actions bot removed the STATE: Stale An outdated issue that will be automatically closed by the Stale bot. label Aug 2, 2022
Copy link

This issue has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this issue in the future. If it still affects you or you have any additional information regarding it, please leave a comment and we will keep it open.

@github-actions github-actions bot added the STATE: Stale An outdated issue that will be automatically closed by the Stale bot. label Mar 16, 2024
Copy link

We're closing this issue after a prolonged period of inactivity. If it still affects you, please add a comment to this issue with up-to-date information. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FREQUENCY: level 1 STATE: Stale An outdated issue that will be automatically closed by the Stale bot. TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

8 participants