In order to update particular snapshot, you can pass name as an argument to your script test command. In package.json “test”: “jest –verbose” In command line npm test “<spec name>” — -u OR npm test “<spec name>” — –updateSnapshot
react-markdown is shipped as js, add babel-jest as a transformer in your jest config transform: { ‘^.+\\.ts?$’: ‘ts-jest’, “^.+\\.(js|jsx)$”: “babel-jest” },
You can use a combination of arrayContaining and objectContaining to make this work. Reference: https://jestjs.io/docs/expect#expectarraycontainingarray https://jestjs.io/docs/expect#expectobjectcontainingobject Here is some sample code for you: function something(a, b, somefn) { somefn([{ x: a, y: b, id: ‘some-guid’ }]); } test(‘Testing something’, () => { const mockSomeFn = jest.fn(); something(2, 3, mockSomeFn); expect(mockSomeFn).toHaveBeenCalledWith( expect.arrayContaining([ expect.objectContaining({ x: 2, y: … Read more
That issue is caused by many updates inside Component. I got the same, this is how I solved the issue. await act( async () => { fireEvent.change(fileInput, { target: { files: [file] } }); });
This is how I was able to get rid of the annoying warning: Include RouterLinkStub, eg.: import { shallowMount, createLocalVue, RouterLinkStub } from ‘@vue/test-utils’; Map NuxtLink stub to RouterLinkStub const wrapper = shallowMount(TestItem, { … stubs: { NuxtLink: RouterLinkStub } }) And in case you were checking nuxt-link text or something, change: const link = … Read more
5 months later I’m coming back to answer my question (I’ve learned a lot since posting this question lol)…. First of all, since it is 5 months later I want to underscore that it is better to use the userEvent library instead of fireEvent if possible. I also would be remiss to not call out … Read more
Actually, you don’t need to use Sinon to test debounces. Jest can mock all timers in JavaScript code. Check out following code (it’s TypeScript, but you can easily translate it to JavaScript): import * as _ from ‘lodash’; // Tell Jest to mock all timeout functions jest.useFakeTimers(); describe(‘debounce’, () => { let func: jest.Mock; let … Read more
The following worked for me: import userEvent from “@testing-library/user-event”; import { render } from “@testing-library/react”; test(“should submit when pressing enter”, () => { const handleSubmit = jest.fn(); const { getByLabelText } = render(<App handleSubmit={handleSubmit} />); const input = getByLabelText(“Name:”); userEvent.type(input, “abc{enter}”); expect(handleSubmit).toHaveBeenCalled(); });
jest.mock is hoisted above import when used at top level and hoisted to the the beginning of the block when used in a block (test function scope, etc), same for jest.unmock. jest.doMock and jest.dontMock serve the same purpose but aren’t hoisted. This would matter for a case like this one: it(‘should mock the module a … Read more