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

Tunnel never closes and test never stops running #95

Open
arvedjo opened this issue Oct 4, 2023 · 7 comments
Open

Tunnel never closes and test never stops running #95

arvedjo opened this issue Oct 4, 2023 · 7 comments

Comments

@arvedjo
Copy link

arvedjo commented Oct 4, 2023

Hi DevExpress,

after updating from testcafe-browser-provider-saucelabs 2.0.0 to 3.0.0 the tunnel never closes and the test runs until timeout. This is reproducible for the following test:

import { Selector } from "testcafe";

fixture`Fixture`.page("http://example.com");

test("test", async (t) => {
  await t.click("body").expect(Selector("h1").innerText).eql("Example Domain");
});

I am tried it an Windows and a Debian docker. I am running on Saucelabs European Server.

This is the run command:

npx testcafe saucelabs:safari .\test\basic_test\ExampleTest.js

This is the console log which stops and runs until saucelabs timeout:
`
Running tests in:

Fixture
√ test
`
Thank you for your support.

@JoergHeinicke5005
Copy link

We are facing the same issue as well in several of our test suites.

@github-actions
Copy link

github-actions bot commented Oct 6, 2023

We appreciate you taking the time to share the information about this issue. We replicated it, and it is currently in our internal queue. Please note that the research may take time. We'll update this thread once we have news.

@arvedjo
Copy link
Author

arvedjo commented Dec 12, 2023

Hi,
are there any updates on the issue?
Thanks Arved

Copy link

No updates yet. Once we make more progress, we will leave a comment.

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.

@JoergHeinicke5005
Copy link

This ticket shouldn't get closed due to some automatic process, but rather taken care of. Multiple users are confirming the issue in their tests.

@arvedjo
Copy link
Author

arvedjo commented Jun 11, 2024

Agree, please fix it. Still testing with old release with many deprecated dependencies to keep tests running.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants