Disable native automation and caching breaks lru-cache

[fredrikkarlsson-pervanovo]

What is your Scenario?

Running tests with config:

• disableNativeAutomation: true
• cache: true

What is the Current behavior?

1) Unhandled promise rejection:
      
      TypeError: sizeCalculation return invalid (expect positive integer)
      at LRUCache.#requireSize (***\node_modules\testcafe\node_modules\lru-cache\src\index.ts:1596:19)
      at LRUCache.set (***\node_modules\testcafe\node_modules\lru-cache\src\index.ts:2041:35)
      at Object.add (***\node_modules\testcafe\node_modules\testcafe-hammerhead\lib\request-pipeline\cache.js:45:19)
      at RequestPipelineContext._addTemporaryEntryToCache (***\node_modules\testcafe\node_modules\testcafe-hammerhead\lib\request-pipeline\context\index.js:137:22)
      at RequestPipelineContext.pipeNonProcessedResponse (***\node_modules\testcafe\node_modules\testcafe-hammerhead\lib\request-pipeline\context\index.js:379:18)
      at processTicksAndRejections (node:internal/process/task_queues:95:5)
      at Array.decideOnProcessingStrategy (***\node_modules\testcafe\node_modules\testcafe-hammerhead\lib\request-pipeline\stages.js:89:17)
      at run (***\node_modules\testcafe\node_modules\testcafe-hammerhead\lib\request-pipeline\index.js:20:9)

      Browser: Chrome 143.0.0.0 / Windows 11

What is the Expected behavior?

Not crashing

What is the public URL of the test page? (attach your complete example)

What is your TestCafe test code?

import { Selector } from "testcafe";

fixture`Bug`;

test("test", async t => {
  await t.navigateTo("https://www.bjelin.se");
  await t.wait(2000);
  await t.expect(Selector("div#root").exists).ok();
});

Your complete configuration file

{
  "browser": "chrome",
  "disableNativeAutomation": true,
  "cache": true
}

Your complete test report

npx testcafe chrome Bug.test.ts 
 Running tests in:
 - Chrome 143.0.0.0 / Windows 11

 Bug
 × test

   1) Unhandled promise rejection:
      
      TypeError: sizeCalculation return invalid (expect positive integer)
      at LRUCache.#requireSize (C:\Users\flomm\Documents\Pervanovo\testcafe-bug\node_modules\testcafe-hammerhead\node_modules\lru-cache\src\index.ts:1596:19)
      at LRUCache.set (C:\Users\flomm\Documents\Pervanovo\testcafe-bug\node_modules\testcafe-hammerhead\node_modules\lru-cache\src\index.ts:2041:35)
      at Object.add (C:\Users\flomm\Documents\Pervanovo\testcafe-bug\node_modules\testcafe-hammerhead\lib\request-pipeline\cache.js:45:19)
      at RequestPipelineContext._addTemporaryEntryToCache
      (C:\Users\flomm\Documents\Pervanovo\testcafe-bug\node_modules\testcafe-hammerhead\lib\request-pipeline\context\index.js:137:22)
      at RequestPipelineContext.pipeNonProcessedResponse
      (C:\Users\flomm\Documents\Pervanovo\testcafe-bug\node_modules\testcafe-hammerhead\lib\request-pipeline\context\index.js:379:18)
      at processTicksAndRejections (node:internal/process/task_queues:95:5)
      at Array.decideOnProcessingStrategy (C:\Users\flomm\Documents\Pervanovo\testcafe-bug\node_modules\testcafe-hammerhead\lib\request-pipeline\stages.js:89:17)
      at run (C:\Users\flomm\Documents\Pervanovo\testcafe-bug\node_modules\testcafe-hammerhead\lib\request-pipeline\index.js:20:9)

      Browser: Chrome 143.0.0.0 / Windows 11



 1/1 failed (3s)

Screenshots

No response

Steps to Reproduce

1. npx testcafe chrome Bug.test.ts

TestCafe version

3.7.3

Node.js version

v20.19.5

Command-line arguments

testcafe chrome Bug.test.ts

Browser name(s) and version(s)

Chrome 143.0.0.0

Platform(s) and version(s)

Windows 11

Other

It have worked for a long time in our CI pipeline with 3.7.0 and seems broken in >= 3.7.1

[Bayheck]

Hello,

I did not manage to reproduce the issue. I attached a project that I used to run the tests. Could you please check if you can reproduce the issue with it?

To run the test, use the following commands:

1. npm i
2. npm run test

If you cannot reproduce the issue, please modify the attached project so that we can reproduce the problematic behavior with it on our side.

I look forward to your response.

cache-issue.zip

[fredrikkarlsson-pervanovo]

I can reproduce it with this:
cache-issue.zip

Just added testcafe 3.7.4 devDep and added "test" script to package.json to your example.
I guess you can increase the wait in the test, but I dont need a higher value to get the error.

[github-actions]

We appreciate you taking the time to share information about this issue. We reproduced the bug and added this ticket to our internal task queue. We'll update this thread once we have news.