Move jest timeout outside test

[bidoubiwa]

Because #713 also timeoud like usual I dig into the same problem again.
I think maybe it is due to the fact that it is not the tests that timeout but the whole jest setup.
So I tried following this stack overflow:
https://stackoverflow.com/questions/49603939/message-async-callback-was-not-invoked-within-the-5000-ms-timeout-specified-by

who suggests the following:

But this would be specific to the test. Or you can set up the configuration file for the framework.

Configuring Jest

// jest.config.js
module.exports = {
// setupTestFrameworkScriptFile has been deprecated in
// favor of setupFilesAfterEnv in jest 24
setupFilesAfterEnv: ['./jest.setup.js']
}

// jest.setup.js
jest.setTimeout(30000)

[curquiza]

Could you remind me the difference between this 30000 and the one in the jest-setup.js file please? (sorry)

[bidoubiwa]

The timeout you specify here needs to be shorter than the default timeout.

The 30000 in the test function was greater than the default timeout of jest which is at 5000. So it was not taken into account.

The 30000 on the test function is linked to the specific test, which means that the test can not take longer than 30000 ms. The jest.timeout function is a global timeout for all tests.

It is not stated clearly in the docs, I'm not sure if I should leave that number in both function:

similarities here: jestjs/jest#5055 (comment)
jestjs/jest#5055 (comment)

[curquiza]

The 30000 on the test function is linked to the specific test, which means that the test can not take longer than 30000 ms. The jest.timeout function is a global timeout for all tests.

So what is the point to add a timeout of 30000 specific to the test if the default timeout value is already exactly 30000? I would understand if you would have added a value of 40000 specific to the test, for example.

[bidoubiwa]

Yes, sorry I was editing my previous comment. Let's remove and figure out if that fixes the issue. If not I'll make an issue on their repo

[curquiza]

bors try

[bors]

try

Build succeeded:

• integration-tests (Node.js 10)
• integration-tests (Node.js 14)
• linter-check
• integration-tests (Node.js 12)

[curquiza]

I let you merge @bidoubiwa!

[bidoubiwa]

bors merge

[bors]

Build succeeded:

• linter-check
• integration-tests (Node.js 10)
• integration-tests (Node.js 12)
• integration-tests (Node.js 14)