-
Love the library. It is much more ergonomic compared to the mocking I was doing by hand!
Jest can show a diff between the received and actual calls when I use `.toHaveBeenCalledWith(...)` including…
-
Thank you to all for the work on this project.
The JSR page for @std/expect states "Jest compatible `expect` assertion functions"
While trying to use `toMatchObject` I noticed it doesn't seem to…
-
### 🚀 Feature Proposal
_This is a copy of the issue https://github.com/jestjs/jest/issues/14700 with slight modifications._
Making all matchers available as asymmetric matchers.
### Motivation
H…
-
> ⚠️⚠️⚠️ IMPORTANT: This is an epic that serves as a template for smaller scoped issues where you perform the refactoring work explained here in a few places of the code only (instead of going all out…
-
Hi,
Like previously exposed (on twitter), I'm working with Jest on Angular. Are you interested in migrating the current matchers for the Jest world?
I will do a PR if you're ok.
Thanks
-
# Description
In order to move towards a test driven development style, especially with the development of the matchmaking system, install [_Jest_](https://jestjs.io) and [_React Testing Library_](ht…
-
### Introduction
Jest lets you define your own custom matchers for the `expect` global namespace. The idea here is to debate the viability for such matchers.
### Example
```js
// proposed API
t…
-
Hello and thanks for this great lib 🙌
On my project we went from `jest` to `vitest`, mainly for performances. Sadly, we lost the `toHaveReceivedCommand` matchers in the process 🥲
Would be awesom…
-
I would expect something like this to be flagged in error, and ideally auto-fixable
```javascript
// bad
expect(example).toStrictEqual(expect.any(Function));
expect(typeof example).toBe('functio…
-
### Clear and concise description of the problem
Currently there is no way to test whether a spy is only called once with certain arguments but both assertions are essential.
This currently requires…