fix: incorrect behaviour of toBeDefined with not flag

vitest-dev · Dec 29, 2021 · 97abcb9 · 97abcb9
1 parent 577ff67
commit 97abcb9
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 0 deletions.
diff --git a/packages/vitest/src/integrations/chai/jest-expect.ts b/packages/vitest/src/integrations/chai/jest-expect.ts
@@ -194,6 +194,12 @@ export const JestChaiExpect: ChaiPlugin = (chai, utils) => {
     return this.be.null
   })
   def('toBeDefined', function() {
+    const negate = utils.flag(this, 'negate')
+    utils.flag(this, 'negate', false)
+
+    if (negate)
+      return this.be.undefined
+
     return this.not.be.undefined
   })
   def('toBeInstanceOf', function(obj: any) {

diff --git a/test/core/test/jest-expect.test.ts b/test/core/test/jest-expect.test.ts
@@ -6,7 +6,10 @@ describe('jest-expect', () => {
   it('basic', () => {
     expect(1).toBe(1)
     expect(null).toBeNull()
+    expect(1).not.toBeNull()
     expect(null).toBeDefined()
+    expect(undefined).not.toBeDefined()
+    expect(undefined).toBeUndefined()
     expect(null).not.toBeUndefined()
     expect([]).toBeTruthy()
     expect(0).toBeFalsy()