Timeout Reason

🚀 Feature Proposal

Perhaps there is already a way to do this, but it would be nice if functions could register reasons for tiemouts. For example, let’s say I have waitElementToBecomeVisible():

await waitElementToBecomeVisible("selector");

waitElementToBecomeVisible could do something like:

async function waitElementToBecomeVisible(selector)
{
    jest.pushTimeoutReason(`An element matching ${selector} did not become visible in the timeout`);
    // ...

    jest.popTimeoutReason();
}

Motivation

More friendly test failures.

Example

See above.

Pitch

Since it interacts with the default timeout. If each method had its own timeout, then this wouldn’t be necessary, but a global timeout necessitates transferring information.

[SimenB]

await expect(functionThatReturnsAPromise).toResolveWithinMs(4500), and we could ignore rejections?

It would be awesome if it could query the timeout of the test though - if the test times out the stack trace will point to the test itself, not the specific expect.

A jest.waitFor(func) that was aware of the test’s timeout would be pretty sweet, I think, even though I like the idea of a matcher

[github-actions[bot]]

This issue was closed because it has been stalled for 7 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.