jest-extended
jest-extended copied to clipboard
jest-community
Additional Jest matchers 🃏💪
## Feature Request ### Description: **The case:** I've got a function (named `parallel`) which runs a list of functions one by one. If one of them crashes, `parallel` will catch...
# Feature Request ## Description Well, not a technical feature request, more an ease of life thing that could mean more movement on Issues/PRs. From what I gather @mattphillips is...
**Feature Request** Description: We have a need on my project to verify that an object matches the general shape of a shapshot. We don't care about any of the property...
**Feature Request** Add a matcher something like naming `toEqualIgnoreArrayItemsOrder` which we can ignore the order of array items when we compare them. **Description**: Unlike [toIncludesSameMembers](https://github.com/jest-community/jest-extended#toincludesamemembersmembers), this function compares objects. If...
VSCode do not support this How can I make it intellisense? 
**Bug** - `package` version: ^0.11.5 - `node` version: v12.14.0 - `yarn` version: 1.19.1 Relevant code or config ```javascript expect(a).toHaveBeenCalledAfter(b) ``` What you did: ```sh yarn flow ``` What happened (please...
**Bug** - `package` version: 0.11.2 - `node` version: v12.13.0 - `npm` (or `yarn`) version: 6.12.0 Relevant code or config See steps. What you did: Following this guide: https://github.com/jest-community/jest-extended/issues/172 The `global.d.ts`...
### Describe the feature you'd like: Jest-Extended has an assertion named the same as jest-extended's one: -> https://github.com/jest-community/jest-extended#tobeempty -> https://github.com/testing-library/jest-dom#tobeempty When both libs are used in the same project, in...
**Bug** - `package` version: 0.11.5 - `node` version: irrelevant - `npm` (or `yarn`) version: irrelevant Relevant code or config ```javascript npm i [email protected] @types/[email protected] [email protected] -E ``` What you did:...
Jest already has a `toBeNaN` matcher, which I'm assuming was added after `jest-extended`s was. Is there any reason to keep the one in `jest-extended` around?
