-
> ⚠️⚠️⚠️ 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…
-
### 🚀 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…
-
# 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…
-
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
-
### 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…
-
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…
-
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 …
-
### 🚀 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…
-
**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…
-
- `@testing-library/jest-dom` version: 6.1.3
- `node` version: 18.15.0
- `jest` (or `vitest`) version: vitest 0.34.4
- `npm` (or `yarn`) version: npm 9.5.0
### Relevant code or config:
…