You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems as if something broke when upgrading from 0.30.1 to 0.31.1 with the test timeouts. Passing { timeout: XXX } to describe does not have an effect any longer, the default testTimeout is always used.
describe("the submitted issue",()=>{test("true is true after 10s",async()=>{awaitnewPromise((resolve)=>setTimeout(resolve,10000));expect(true).toBe(true);});},{timeout: 30000,});
I'm expecting the test to pass after approx 10s instead it fails after 5s with the error:
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
marcus13371337
changed the title
timeout to describe does not have an effect in 0.31
Setting a timeout to a describe does not have an effect in 0.31May 26, 2023
Describe the bug
It seems as if something broke when upgrading from
0.30.1
to0.31.1
with the test timeouts. Passing{ timeout: XXX }
todescribe
does not have an effect any longer, the defaulttestTimeout
is always used.Reproduction
Run the foll
Short description:
I'm expecting the test to pass after approx 10s instead it fails after 5s with the error:
System Info
Used Package Manager
pnpm
Validations
The text was updated successfully, but these errors were encountered: