0

I have node 12.14.0, npm 6.13.4 and testcafe 1.7.1 in my Windows 10 PC.

I am trying to run a basic sample script using the command testcafe chrome test1.js:

import { Selector } from 'testcafe';

fixture `Getting Started`
    .page `http://devexpress.github.io/testcafe/example`;

test('My first test', async t => {
    // Test code
});

It takes about 2 minutes everytime for the browser to be triggered. The test runs fine after that though.

What could be causing this delay? I also tried running it through npm command and got the same result.

Alex Skorkin
  • 4,264
  • 3
  • 25
  • 47
Janaaaa
  • 1,346
  • 1
  • 16
  • 34
  • 2
    Could you please clarify if this issue occurs with other browsers? Also, I suggest you run Chrome as a [portable browser](https://devexpress.github.io/testcafe/documentation/using-testcafe/command-line-interface.html#portable-browsers) by the full path: `testcafe "path:\`C:\Program Files (x86)\Google\Chrome\Application\chrome.exe\`" test.js` – Dmitry Ostashev Jan 03 '20 at 08:45
  • Yes, it was occurring with other browsers too. the full path didn't work either. But downgrading the testcafe version to 1.6.1 fixed the problem (atleast for now). I will post back if i find anything else. – Janaaaa Jan 03 '20 at 17:06
  • Thank you for the update. Try disabling the antiviral software if you have any when you start TestCafe and see if it makes any difference. – Alex Skorkin Jan 06 '20 at 09:39
  • Thank you. I tried turning off the antivirus software with Testcafe 1.7.1 but no luck. With Testcafe 1.6.1, it is running fine. – Janaaaa Jan 07 '20 at 01:11
  • 1
    Until now, our attempts to replicate this issue were unsuccessful. Only the very first browser start can be slowed down, but it works quickly after all. You might want to try disabling firewall and other similar protection tools if you have any. – Alex Skorkin Jan 07 '20 at 08:39
  • I've found the same issue, when I found this post I tried downgrading to 1.6.1 and my tests started in about 10s, vs 2min + for any version/latest above that. Janaaaa, did you find a resolve for this? – Jamie Kemp Jun 05 '20 at 08:31
  • @Jamie Kemp Could you please share the full command line with which you start your tests? Also, I'd appreciate it if you capture a video during the test launching process with the Task Manager window opened (to see the CPU usage of processes). This will help us determine the cause of the issue. – Dmitry Ostashev Jun 08 '20 at 09:00

0 Answers0