TestCafe hangs on loading page and freezes execution when executing concurrently

What is your Scenario?

Concurrently run 5 fixtures that execute a single test. Visiting https://uk.zwift.com results in TC hanging indefinitely and preventing the remainder of test execution.

What is the Current behavior?

TestCafe hangs on page load

What is the Expected behavior?

Pages are loaded concurrently as expected

What is your public website URL? (or attach your complete example)

https://github.com/vlads11/TC-PageLoadError

1. npm install
2. testcafe chrome ./Tests/* -c 5 --skip-js-errors

This may need to be triggered a few times but it consistently reproduces

What is your TestCafe test code?

Test Code provided https://github.com/vlads11/TC-PageLoadError ----- this single fixture is duplicated 5 times to reproduce the error in question.

import { Selector } from “testcafe”; import { test } from ‘testcafe’;

let homeURL = ‘https://uk.zwift.com’;

//slice0 let slice0 = Selector(‘[class='image-with-text-overlay__banner columns one-whole image-crop-none']’)

fixture Shopify HowZwiftWorkspage .page(‘about:blank’) .beforeEach(async t => { await t.navigateTo(homeURL); })

test(‘Slice0 Get Started Button goes to Create Account page’, async t => { await t.click(slice0); })

Your complete configuration file

default

Your complete test report

No response

Screenshots

Recording of issue can be seen here: https://github.com/vlads11/TC-PageLoadError/blob/main/ScreenRecording.mov

Steps to Reproduce

1. Navigate to https://uk.zwift.com with a concurrent session count of 3 or higher
2. Notice page hang and never completes loading.

TestCafe version

1.18.6

Node.js version

v16.14.2

Command-line arguments

testcafe chrome ./Tests/* -c 5 --skip-js-errors

Browser name(s) and version(s)

Chrome 101

Platform(s) and version(s)

macOS 12.3.1 but also happens in Linux

Other

No response

[Aleksey28]

Hi @vlads11,

We don’t have any results yet and we can’t give you any time estimates. We are fixing issues according to our queue. Right now, we are not working on this issue. We will update this thread once we have any news.

[Aleksey28]

I see. We don’t have a workaround for this case yet; you can only decrease concurrency.