I was struggling with the same problem and actually it turns out that a simple change seems to do the trick. I just updated the moduleDirectories field in jest.config.js. Before moduleDirectories: [‘node_modules’] After moduleDirectories: [‘node_modules’, ‘src’] Hope it helps.
You can easily do that with react-testing-library. First, you have to understand that container or the result of getByText etc. are merely DOM nodes. You can interact with them in the same way you would do in a browser. So, if you want to know what class is applied to container.firstChild you can just do … Read more
From the documentation you need to add modulePathIgnorePatterns which is an array of string values which will be matched against modulePathIgnorePatterns [array<string>] # (default: []) An array of regexp pattern strings that are matched against all module paths before those paths are to be considered ‘visible’ to the module loader. If a given module’s path … Read more
You can try: global.window = Object.create(window); const url = “http://dummy.com”; Object.defineProperty(window, ‘location’, { value: { href: url } }); expect(window.location.href).toEqual(url); Have a look at the Jest Issue for that problem: Jest Issue
There is no built-in method to compare arrays without comparing the order, but you can simply sort the arrays using .sort() before making a comparison: expect([“ping wool”, “diorite”].sort()).toEqual([“diorite”, “pink wool”].sort()); You can check the example in this fiddle.
Thanks to @sdgluck for the answer, though I would like to add to this answer that in my case, I wanted a clear state after each tests since I have multiple tests with same spy. So instead of calling the mockClear() in previous test(s), I moved it into the afterEach() (or you can use it … Read more
Jest parallelizes test runs and it doesn’t know upfront which tests it should run and which it shouldn’t run. This means when you use “fit”, it will only run one test in that file. But it still runs all other test files in your project. fit, fdescribe and it.only, describe.only have the same purpose: skip … Read more
I found the answer here https://devhints.io/jest test(‘it is raining’, () => { expect(inchesOfRain()).toBeGreaterThan(0); }); test.skip(‘it is not snowing’, () => { expect(inchesOfSnow()).toBe(0); }); Link on off doc
The highlight of this answer is jest.requireActual(), this is a very useful utility that says to jest that “Hey keep every original functionalities intact and import them”. jest.mock(‘./utilities.js’, () => ({ …jest.requireActual(‘./utilities.js’), speak: jest.fn(), })); Let’s take another common scenario, you’re using enzyme ShallowWrapper and it doesn’t goes well with useContext() hook, so what’re you … Read more
The Jest documentation now has an “official” workaround: Object.defineProperty(window, ‘matchMedia’, { writable: true, value: jest.fn().mockImplementation(query => ({ matches: false, media: query, onchange: null, addListener: jest.fn(), // Deprecated removeListener: jest.fn(), // Deprecated addEventListener: jest.fn(), removeEventListener: jest.fn(), dispatchEvent: jest.fn(), })), }); Mocking methods which are not implemented in JSDOM