-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing jest timers, test.each, and module mocks #3594
Comments
Uhm, could you provide more information about what you mean? bun test is already implemented. |
Regarding test.each it's being tracked in #3622 |
@TiranexDev I get the following error in bun test |
Probably because bun doesn't implement it, just wait a bit and we will get it done |
Just coming here to say |
We're using a few other timer functions which seem to be missing:
|
I didn't try it, but is module mocking already possible in bun-test? |
No, it is not implemented. There is a separate issue that tracks all of the
test implementations that are in progress, and it is not listed there at
all, currently.
I recently posted on that issue thread, asking to add it to the list - but
haven't gotten a response, yet. I think the maintainers are pretty busy at
the moment with the post launch buzz :)
…On Sun, Sep 10, 2023, 09:32 Jonas Strassel ***@***.***> wrote:
I didn't try it, but is module mocking
<https://jestjs.io/docs/manual-mocks#mocking-node-modules> already
possible in bun-test?
—
Reply to this email directly, view it on GitHub
<#3594 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC5R27AWHETRAG5D27QVQZ3XZXTRZANCNFSM6AAAAAA2EVP3QE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
any news on this? full support for jest would be great |
module mocks and test.each are implemented timers are still missing |
I see "resetModules" have been strikedthrough, but I cannot find a way to achieve this functionality, does anybody know how? |
@manast sorry also fail for me. removed the strikedthrough. |
What is the problem this feature would solve?
we could use it for tests
What is the feature you are proposing to solve the problem?
TypeError: jest.runAllTimers is not a function.
TypeError: it.each is not a function.TypeError: jest.resetModules is not a function.
What alternatives have you considered?
No response
The text was updated successfully, but these errors were encountered: