111

I'm developping a reactJs application. I'm using jest to test my application. I want to test a function that download a blob.

But unfortunately I receve this error:

URL.createObjectURL is not a function

my test function:

describe('download', () => {
    const documentIntial = { content: 'aaa' };
    it('msSaveOrOpenBlob should not have been called when navigao is undefined', () => {
      window.navigator.msSaveOrOpenBlob = null;
      download(documentIntial);
      expect(window.navigator.msSaveOrOpenBlob).toHaveBeenCalledTimes(0);
    });
  });

The function I want to test:

export const download = document => {
  const blob = new Blob([base64ToArrayBuffer(document.content)], {
    type: 'application/pdf',
  });
  if (window.navigator && window.navigator.msSaveOrOpenBlob) {
    window.navigator.msSaveOrOpenBlob(blob);
    return;
  }

  const fileURL = URL.createObjectURL(blob);
  window.open(fileURL);
};
2

8 Answers 8

109

This would appear to be as simple as setting up URL on the Global in Jest. Something like

describe('download', () => {
  const documentIntial = { content: 'aaa' };
  global.URL.createObjectURL = jest.fn();
  it('msSaveOrOpenBlob should not have been called when navigao is undefined', () => {
    global.URL.createObjectURL = jest.fn(() => 'details');
    window.navigator.msSaveOrOpenBlob = jest.fn(() => 'details');
    download(documentIntial);
    expect(window.navigator.msSaveOrOpenBlob).toHaveBeenCalledTimes(1);
  });
});

This should result in a test that you can also use for checking if global.URL.createObjectURL was called. As a side note: you may also run into a similar issue with window.open I would suggest mocking that as well if this becomes the case.

Sign up to request clarification or add additional context in comments.

3 Comments

I have this result : expect(jest.fn())[.not].toHaveBeenCalledTimes() jest.fn() value must be a mock function or spy. Received: undefined
Take a look at that I actually tested it this time. You should not be nulling the msSaveOrOpenBlob. You will want to mock it to be able to tell how often it has been called... otherwise it is not going to give you a call count.
for those wanted to achieve the same with vitest instead of jest this will also work as long as you set globals: true on vitest.config vitest.dev/config/#globals
37

Since window.URL.createObjectURL is not (yet) available in jest-dom, you need to provide a mock implementation for it.

Don't forget to reset the mock implementation after each test.

describe("your test suite", () => {
  window.URL.createObjectURL = jest.fn();

  afterEach(() => {
    window.URL.createObjectURL.mockReset();
  });

  it("your test case", () => {
    expect(true).toBeTruthy();
  });
});

1 Comment

You meant: not (yet) available in js-dom
20

jsdom, the JavaScript implementation of the WHATWG DOM used by jest doesn't implement this method yet.

You can find an open ticket about this exact issue on their github page where some workarounds are provided in comments. But if you need the blobURL to actually work you'll have to wait this FR is solved.

Workaround proposed in the comments of the issue for jest:

function noOp () { }
if (typeof window.URL.createObjectURL === 'undefined') { 
  Object.defineProperty(window.URL, 'createObjectURL', { value: noOp})
}

Comments

19

You just have to Write this in your setupTest.js

window.URL.createObjectURL = function() {};

1 Comment

This finally worked for me when several other options didn't.
10

Just mocking the function global.URL.createObjectURL did not work for me, because the function was used by some modules during import and I got the error Jest URL.createObjectURL is not a function during import.

Instead it did help to create a file mockJsdom.js

Object.defineProperty(URL, 'createObjectURL', {
  writable: true,
  value: jest.fn()
})

Then import this file as the first import in your file containing the test

import './mockJsdom'
import { MyObjects} from '../../src/lib/mylib'

test('my test', () => {
  // test code
}

Found here: https://jestjs.io/docs/manual-mocks#mocking-methods-which-are-not-implemented-in-jsdom

2 Comments

I wrote the mock function just before starting of the test suite. That too worked. Thanks a lot for this useful answer and reference link as well.
Also add "import {jest} from '@jest/globals';" at the top of mockJsdom file. From : jestjs.io/docs/ecmascript-modules
7

The package jsdom-worker happens to provide this method, as well as adding support for web workers. The following worked for me:

npm install -D jsdom-worker

Then in package.json, edit or add a jest key:

{
  ...
  "jest": {
    "setupFiles": [
      "jsdom-worker"
    ]
  }
}

2 Comments

Out of the box, Create React App does not support overriding the Jest option "setupFiles".
@Hultan but you can create an isolate jest.config.js file, which is better to isolate functionality
1

Using react-testing-library with jest:

I had to add jest.spyOn(URL, 'createObjectURL').mockImplementation(); inside my test. This worked in conjunction with creating a mock file for the dom object

Object.defineProperty(URL, 'createObjectURL', {writable: true, value: jest.fn()})

and adding the import statement for that mock file as the first import inside my testing file.

Note: the mock file cannot be inside the tests directory

Comments

1

this code simulates a blob url to test your full cycle

    global.URL.createObjectURL = jest.fn(
      (blob: any) => `blob:${blob.size}#t=${Date.now()}`
    )

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.