Fix: Consistent Use of testTimeout in Jest Configurations

[PrinceSajjadHussain]

The testTimeout property is used to define the maximum time a test can run before Jest considers it a failure. While some jest.config.js files define it (e.g., packages\cli\jest.config.js and packages\@n8n\ai-workflow-builder\jest.config.js), others do not. For consistency and to ensure tests do not run indefinitely, it is good practice to define a default testTimeout in the root jest.config.js so all packages inherit it.

Applied fixes:
--- a/jest.config.js
+++ b/jest.config.js
@@ -50,6 +50,7 @@
collectCoverage: isCoverageEnabled,
coverageReporters: ['text-summary', 'lcov', 'html-spa'],
workerIdleMemoryLimit: '1MB',

• testTimeout: 5_000, // Default timeout for tests in milliseconds
  };

if (process.env.CI === 'true') {

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cubic-dev-ai]

cubic reviewed 1 file and found no issues. Review PR in cubic.dev.

_{React with 👍 or 👎 to teach cubic. Tag @cubic-dev-ai to give specific feedback.}

[PrinceSajjadHussain]

please Approve it @tcurdt @marksteve @ceefour

[Joffcom]

Hey @PrinceSajjadHussain,

Thanks for the PR, We have created "GHC-2675" as the internal reference to get this reviewed.

One of us will be in touch if there are any changes needed, in most cases this is normally within a couple of weeks but it depends on the current workload of the team.

[Memoona-Qaiser]

👀