Skip to content
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

Jest got a new mock #2443

Closed
Biki-das opened this issue Feb 5, 2022 · 2 comments
Closed

Jest got a new mock #2443

Biki-das opened this issue Feb 5, 2022 · 2 comments

Comments

@Biki-das
Copy link

Biki-das commented Feb 5, 2022

jestjs/jest#12285

@fatso83
Copy link
Contributor

fatso83 commented Feb 7, 2022

This issue is lacking relevant information, preventing it from being worked on


The reason we have an issue template is for issues to have sufficient detail to be able to be worked on.

This issue lacks some or all of the information needed for us to do something meaningful about it.

We usually ask for this to be provided:

  • Sinon version :
  • Environment :
  • Example URL :
  • Other libraries you are using:

What did you expect to happen?

What actually happens

How to reproduce

Describe in sufficient detail how to reproduce the faulty behaviour for the person that should choose to work on the problem

Really long code sample or stacktrace
If you need to provide a dump of a stack trace or
other lengthy material, such as 80 lines of example code,
please stuff it in a `<details>` tag such as this
to make the issue more readable. Thanks.

@fatso83 fatso83 closed this as completed Feb 7, 2022
@fatso83
Copy link
Contributor

fatso83 commented Feb 7, 2022

Ah, I checked out the link. You implemented lastCall for Jest. Good for them 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants