-
Jest supports asynchronous matchers and asymmetric matchers, two required things to port expect-puppeteer matchers into Jest matchers. Some problems still persist:
**Some matchers are returning an …
-
# Bug report
## Packages affected
- [x] sandpack-client
- [x] sandpack-react
## Description of the problem
Custom asymmetric matchers break in Sandpack, because they're not being call…
-
We are using tsup in storybook, but we seem to have a problem with the declaration files emitted by tsup.
This is a minimal reproduction of the file:
```ts
import { default as expectPatched } f…
-
**The problem**
I'm working to replace jest with vitest in our current codebase. I'm able to use the @emotion/jest matchers in vitest by simply `expect.extend({ ...matchers });` and it works withou…
-
### 🚀 Feature Request
When this feature gets implemented:
Playwright would provide a generic callback mock that can be passed into components which then later can be asserted using appropriate ass…
-
It would be quite a nice addition if this would support custom matchers from `@testing-library/jest-dom` - many of them are somewhat builtin to Cypress so might be better not to touch them but for exa…
-
I'm trying to test some API calls we make, and was wondering if it's possible to do something like:
```js
expectSaga(fetchData)
.provide(/* mocks */)
// expect.stringContaining below 👇
.c…
-
Hey hey, long time not posted here^^'
## Describe the bug
`toHaveTextContent()` does exact matching by default, while the same helper exposed by [jest-dom](https://github.com/testing-library/jes…
-
This is more of a discussion than a bug or feature request.
I noticed that jest-extended contains some matchers that already exist in the latest Jest. Example:
`toContainKey` === `toHaveProperty`
…
-
https://jestjs.io/docs/using-matchers