jest-community/jest-extended

Issues

• value '...actual' is not correct for toHaveBeenCalledExactlyOnceWith fail case

  #672 opened a year ago by lcialon
  2

• TypeError: expect.toIncludeSameMembers is not a function

  #704 opened 3 months ago by yashna-te
  0

• BUG: toHaveBeenCalledExactlyOnceWith only reports first argument of method call in feedback on a failed assertion.

  #690 opened 7 months ago by GRollason
  1

• `InverseAsymmetricMatchers` incorrectly extends base Jest Expect

  #703 opened 3 months ago by Woodz
  0

• toBeCloseTo fails incorrectly

  #702 opened 4 months ago by bennidi
  2

• Current setup instructions for Vitest don't work for asymmetric matchers' typings

  #649 opened a year ago by acidoxee
  10

• `toHaveBeenCalledExactlyOnceWith` expects an array of objects, when the object is passed as `args`

  #645 opened a year ago by oleksandrva
  7

• TypeScript declarations are not working when used with @jest/globals

  #674 opened a year ago by slavafomin
  1

• toBeInRange bug in implementation

  #670 opened a year ago by lcialon
  5

• Chore: Is there any plan to upgrade yarn to the latest?

  #678 opened 10 months ago by eryue0220
  2

• Simplify typescript recommendations

  #685 opened 9 months ago by silverwind
  4

• Feature Request: `stringContainingCaseInsensitive`

  #686 opened 8 months ago by yasinosman
  0

• Feature Request: Array matcher diff

  #684 opened 9 months ago by didley
  0

• BUG: nested matcher printing "object Object"

  #682 opened 9 months ago by leppaott
  0

• `toContainOneOf([string1, string2, string3])` would be nice

  #679 opened 9 months ago by robertleeplummerjr
  0

• Use jest-diff in toHaveBeenCalledWith matcher results

  #676 opened a year ago by olivierlacan
  0

• Declaration merging does not work without exporting the CustomMatchers interface.

  #652 opened a year ago by cdierkens
  2

• `toIncludeSameMembers` output is hard to understand

  #639 opened a year ago by rluvaton
  2

• Type of `fail` clashes with vitest

  #554 opened a year ago by simon-abbott
  3

• `fail` does not work when testing code using a `try/catch`

  #663 opened a year ago by thehale
  0

• [Bug]: The second param of toHaveBeenCalledBefore/toHaveBeenCalledAfter has default value, but is not typed as optional

  #651 opened a year ago by Yupeng-li
  1

• Type definitions not working

  #526 opened 2 years ago by webstackdev
  16

• Number matches should not coerce non-numbers to numbers.

  #617 opened 2 years ago by paperdave
  1

• TypeScript issue: File '/home/nmurgor/git/bitgesell-node-monitor/node_modules/jest-extended/types/index.d.ts' is not a module.

  #602 opened 2 years ago by naftalimurgor
  2

• Vitest typings override instead of augmenting module

  #610 opened a year ago by mlev
  26

• `toEqual` passes on non-equal arrays where trailing undefined

  #630 opened a year ago by overlookmotel
  1

• Feature Request: Support "export" package

  #615 opened 2 years ago by mikicho
  0

• `toHaveBeenCalledOnceWith` incorrectly compares `Map`s

  #589 opened 2 years ago by beebs93
  1

• `toHaveBeenCalledBefore` and `toHaveBeenCalledAfter` don't accept result of `jest.fn()`

  #552 opened 2 years ago by Lukas-Kullmann
  1

• Better clarify the difference between toIncludeAllMembers and toIncludeSameMembers in the documentation

  #609 opened 2 years ago by rdsedmundo
  0

• Have date related matchers work with dates that are in a string

  #607 opened 2 years ago by JaapHaitsma
  0

• Breaking change in vitest

  #598 opened 2 years ago by GuillaumeRahbari
  0

• Feature reqest: expect.toMatch() to check is string matches RegExp

  #597 opened 2 years ago by mbyrne00
  0

• BigInt support for Number functions

  #591 opened 2 years ago by mcintyre94
  0

• `toHaveBeenCalledOnceWith` naming is ambiguous

  #529 opened 2 years ago by harry-gocity
  5

• Docs: Number page missing toBeNumber on sidebar

  #590 opened 2 years ago by mcintyre94
  0

• How about new matcher combining toHaveBeenCalledTimes and several toHaveBeenNthCalledWith?

  #580 opened 2 years ago by tkxksdl2
  0

• toPartiallyContain matcher throws exception if array contains null/undefined

  #579 opened 2 years ago by MikeWinter
  0

• Received 'Could not find a declaration file for module 'jest-extended/all' when importing jest-extended

  #577 opened 2 years ago by hollygcraig
  0

• 'toHaveBeenCalledOnceWith' error message doesn't handle mismatched argument lengths

  #573 opened 2 years ago by SLKnutson
  1

• toHaveBeenCalledOnceWith

  #561 opened 2 years ago by ascdi
  1

• Type definitions of > v3.2.1 using any type

  #558 opened 2 years ago by aukevanleeuwen
  0

• Rework issue template

  #553 opened 2 years ago by simon-abbott
  0

• [Feauture]: Add geo matchers (toBeGeoLatitude, toBeGeoLongitude)

  #542 opened 2 years ago by verdecchia
  0

• `toHaveBeenCalledOnceWith` does not work with Symbols

  #532 opened 2 years ago by aduponchel
  1

• asymmetric matcher type definitions are not good (yet again)

  #550 opened 2 years ago by hugebdu
  18

• Vitest TypeScript support for InverseAsymmetricMatchers

  #548 opened 2 years ago by rluvaton
  6

• Matchers very slow for large objects

  #544 opened 2 years ago by overlookmotel
  0

• Duplicated page for `toSatisfy` in docs

  #533 opened 2 years ago by MarcellPerger1
  0

• [Feature]: Add Element Colour Contrast Matcher

  #524 opened 2 years ago by jharrilim
  0