React testing lib not update the state - reactjs

My component:
import React from 'react'
const TestAsync = () => {
const [counter, setCounter] = React.useState(0)
const delayCount = () => (
setTimeout(() => {
setCounter(counter + 1)
}, 500)
)
return (
<>
<h1 data-testid="counter">{ counter }</h1>
<button data-testid="button-up" onClick={delayCount}> Up</button>
<button data-testid="button-down" onClick={() => setCounter(counter - 1)}>Down</button>
</>
)
}
export default TestAsync
My test file:
describe("Test async", () => {
it("increments counter after 0.5s", async () => {
const { getByTestId, getByText } = render(<TestAsync />);
fireEvent.click(getByTestId("button-up"));
const counter = await waitForElement(() => getByTestId("counter"));
expect(counter).toHaveTextContent("1");
});
});
After run the test file, I got error said:
Expected element to have text content:
1
Received:
0
I am a little bit confused why I use waitForElement to get the element but why the element still has the old value?
React-testing-lib version 9.3.2

First of all, waitForElement has been deprecated. Use a find* query (preferred: https://testing-library.com/docs/dom-testing-library/api-queries#findby) or use waitFor instead: https://testing-library.com/docs/dom-testing-library/api-async#waitfor
Now, we use waitFor:
waitFor may run the callback a number of times until the timeout is reached.
You need to wrap the assertion statement inside the callback of the waitFor. So that waitFor can run the callback multiple times. If you put the expect(counter).toHaveTextContent('1'); statement outside and after waitFor statement, then it only run once. React has not been updated when assertions run.
Why RTL will run the callback multiple times(run callback every interval before timeout)?
RTL use MutationObserver to watch for changes being made to the DOM tree, see here. Remember, our test environment is jsdom, it supports MutationObserver, see here.
That means when React updates the state and applies the update to the DOM, the changes of the DOM tree can be detected and RTL will run the callback again including the assertion. When the React component states are applied and become stable, the last run of the callback is taken as the final assertion of the test. If the assertion fails, an error is reported, otherwise, the test passes.
So the working example should be:
index.tsx:
import React from 'react';
const TestAsync = () => {
const [counter, setCounter] = React.useState(0);
const delayCount = () =>
setTimeout(() => {
setCounter(counter + 1);
}, 500);
return (
<>
<h1 data-testid="counter">{counter}</h1>
<button data-testid="button-up" onClick={delayCount}>
Up
</button>
<button data-testid="button-down" onClick={() => setCounter(counter - 1)}>
Down
</button>
</>
);
};
export default TestAsync;
index.test.tsx:
import { fireEvent, render, waitFor } from '#testing-library/react';
import React from 'react';
import TestAsync from '.';
import '#testing-library/jest-dom/extend-expect';
describe('Test async', () => {
it('increments counter after 0.5s', async () => {
const { getByTestId } = render(<TestAsync />);
fireEvent.click(getByTestId('button-up'));
await waitFor(() => {
const counter = getByTestId('counter');
expect(counter).toHaveTextContent('1');
});
});
});
Test result:
PASS stackoverflow/71639088/index.test.tsx
Test async
✓ increments counter after 0.5s (540 ms)
-----------|---------|----------|---------|---------|-------------------
File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
-----------|---------|----------|---------|---------|-------------------
All files | 88.89 | 100 | 75 | 88.89 |
index.tsx | 88.89 | 100 | 75 | 88.89 | 17
-----------|---------|----------|---------|---------|-------------------
Test Suites: 1 passed, 1 total
Tests: 1 passed, 1 total
Snapshots: 0 total
Time: 2.307 s

Related

Unable to test combination of useEffect and setTimeout using Jest

Trying to assert a simple state change made using useEffect and setTimeout. The effect calls setTimeout with a value of 1500ms which should change the displayed string from 'unchanged' to 'changed'.
component
import * as React from 'React';
import {useEffect} from 'React';
import {Text, View} from 'react-native';
export function Dummy() {
const [str, changeStr] = React.useState('unchanged');
useEffect(() => {
setTimeout(() => {
changeStr('changed');
}, 1500);
}, []);
return (
<View>
<Text>{str}</Text>
</View>
);
}
test
import {render, waitFor} from '#testing-library/react-native';
import * as React from 'React';
import {Dummy} from '../Dummy';
// Activate fake timers
jest.useFakeTimers();
describe('Dummy', () => {
it('should change the string after 1500 ms', async () => {
const {getByText} = render(<Dummy />);
// run all timers which should fire the state update
jest.runAllTimers();
await waitFor(
() => {
expect(getByText('changed')).toBeTruthy();
},
{timeout: 5000},
);
});
});
result
FAIL src/components/__tests__/dummy.spec.js (8.037 s)
Dummy
✕ should change the string after 1500 ms (5226 ms)
● Dummy › should change the string after 1500 ms
: Timeout - Async callback was not invoked within the 5000 ms timeout specified by jest.setTimeout.Timeout - Async callback was not invoked within the 5000 ms timeout specified by jest.setTimeout.Error:
7 |
8 | describe('Dummy', () => {
> 9 | it('should change the string after 1500 ms', async () => {
| ^
10 | const {getByText} = render(<Dummy />);
11 |
12 | // run all timers which should fire the state update
at new Spec (node_modules/jest-jasmine2/build/jasmine/Spec.js:116:22)
at Suite.<anonymous> (src/components/__tests__/dummy.spec.js:9:3)
anyone know why this is and how I can successfully test this?

update and get new state from setState Hook with Jest

I succeed to create a functional component, to mock the useState function and to get the call to the mocking function. But the functional component keep its initial value. Is there no way at all to get the new functional component created after update with its new initial "useState" value ?
For example, if I do an "simulate(click)" with enzyme twice on the button in the code below, I will have twice the value "1" returned in the mock function.
This limits a lot possible tests.
function Example() {
const [count, setCount] = useState(0);
return (
<div>
<p>Vous avez cliqué {count} fois</p>
<button id="count-up" onClick={() => setCount(count + 1)}>
Cliquez ici
</button>
</div>
);
}
here's my test code :
import React, { useState as useStateMock, setState } from 'react';
import { shallow, mount, render } from 'enzyme';
import Example from './file with example component'
jest.mock('react', () => ({
...jest.requireActual('react'),
useState: jest.fn(),
}));
describe('<Home />', () => {
let wrapper;
const setState = jest.fn();
beforeEach(async () => {
useStateMock.mockImplementation(init => [init, setState]);
wrapper = mount(<Example />)
});
describe('Count Up', () => {
it('calls setCount with count + 1', () => {
wrapper.find('#count-up').first().simulate('click');
expect(setState).toHaveBeenLastCalledWith(1);
wrapper.find('#count-up').simulate('click');
expect(setState).toHaveBeenLastCalledWith(2);
});
});
})
I would like the setState mock function to return 1 then 2 as its corresponds to the initial state 0 + 1 and then this results 1 + 1 again.
But the functional component is not updated, and I don't know how to do that.
Thanks for your help
Because you mock useState without providing an implementation, the functionality of useState has changed.
Don't mock the react module and its implementations. Continue to use their original implementation. You should test the component behavior instead of the implementation detail.
In other words, we want to test from the user's point of view, they don't care about your implementation, they just care about what they can see on the screen.
Component behavior is: What does your component render when the state changes.
So the unit test should be:
Example.tsx:
import React from 'react';
import { useState } from 'react';
export function Example() {
const [count, setCount] = useState(0);
return (
<div>
<p>Vous avez cliqué {count} fois</p>
<button id="count-up" onClick={() => setCount(count + 1)}>
Cliquez ici
</button>
</div>
);
}
Example.test.tsx:
import { mount } from 'enzyme';
import React from 'react';
import { Example } from './Example';
describe('70585877', () => {
test('should pass', () => {
const wrapper = mount(<Example />);
const button = wrapper.find('#count-up');
// The initial state of the component as seen by the user
expect(wrapper.find('p').text()).toEqual('Vous avez cliqué 0 fois');
// User click the button
button.simulate('click');
// The next state of the component as seen by the user
expect(wrapper.find('p').text()).toEqual('Vous avez cliqué 1 fois');
// User click the button again
button.simulate('click');
// The next state of the component as seen by the user
expect(wrapper.find('p').text()).toEqual('Vous avez cliqué 2 fois');
});
});
Test result:
PASS examples/70585877/Example.test.tsx (9.532 s)
70585877
✓ should pass (34 ms)
-------------|---------|----------|---------|---------|-------------------
File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
-------------|---------|----------|---------|---------|-------------------
All files | 100 | 100 | 100 | 100 |
Example.tsx | 100 | 100 | 100 | 100 |
-------------|---------|----------|---------|---------|-------------------
Test Suites: 1 passed, 1 total
Tests: 1 passed, 1 total
Snapshots: 0 total
Time: 10.519 s

write unit test for event handlers that updates some state in react using jest and enzyme

I am trying to write some unit tests for the event handlers that I wrote inside my component. I would like to write tests for the states updates inside that event handlers.
For example I have the following function that are called onMouseDown inside the component. How can I write some tests about that.
const [visible, setVisibility ] = useState(false);
const onSelection = () => {
setVisibility(!visible)
};
<div onMouseDown ={()=> onSelection(items)}>Click</div>
{visible && <div>simple text</div>}
Can anybody guide me through there. Thanks in advance
Suppose the component like this:
index.tsx:
import React, { useState } from 'react';
export default function Example() {
const [visible, setVisibility] = useState(false);
const onSelection = () => {
setVisibility(!visible);
};
return (
<div>
<div onMouseDown={() => onSelection()}>Click</div>
{visible && <div>simple text</div>}
</div>
);
}
We test the behavior of the component from the user's perspective.
We should test: What is the component rendering before triggering the mousedown event and what is rendered after the visible state changes.
index.test.tsx
import { shallow } from 'enzyme';
import React from 'react';
import Example from './';
describe('70577146', () => {
test('should pass', () => {
const wrapper = shallow(<Example />);
const button = wrapper.find('div[children="Click"]');
expect(wrapper.find('div[children="simple text"]').exists()).toBeFalsy();
button.simulate('mousedown');
expect(wrapper.find('div[children="simple text"]').exists()).toBeTruthy();
});
});
Test result:
PASS examples/70577146/index.test.tsx (11.966 s)
70577146
✓ should pass (11 ms)
-----------|---------|----------|---------|---------|-------------------
File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
-----------|---------|----------|---------|---------|-------------------
All files | 100 | 100 | 100 | 100 |
index.tsx | 100 | 100 | 100 | 100 |
-----------|---------|----------|---------|---------|-------------------
Test Suites: 1 passed, 1 total
Tests: 1 passed, 1 total
Snapshots: 0 total
Time: 13.599 s, estimated 14 s

Unit testing a custom hook to ensure that it calls another hook

How can we ensure that a custom hook actually calls a method exposed by another hook?
Let's say, I have a custom hook useName that internally leverages useState.
import { useState } from 'react'
export const useName = () => {
const [name, setState] = useState()
const setName = (firstName: string, lastName: string) => setState([firstName, lastName].join(' '))
return {name, setName}
}
I need to assert that calling setName actually calls `setState'. My test case is written as following:
/**
* #jest-environment jsdom
*/
import * as React from 'react'
import { renderHook, act } from '#testing-library/react-hooks'
import { useName } from './useName'
jest.mock('react')
const setState = jest.fn()
React.useState.mockReturnValue(['ignore', setState]) //overwriting useState
test('ensures that setState is called', () => {
const {result} = renderHook(() => useName())
act(() => {
result.current.setName("Kashif", "Nazar") //I am expecting this to hit jest.fn() declared above.
})
expect(setState).toBeCalled()
})
and I get the following result.
FAIL src/useName.test.ts
✕ ensures that setState is called (3 ms)
● ensures that setState is called
TypeError: Cannot read property 'setName' of undefined
18 |
19 | act(() => {
> 20 | result.current.setName("Kashif", "Nazar")
| ^
21 | })
22 |
23 | expect(setState).toBeCalled()
at src/useName.test.ts:20:24
at batchedUpdates$1 (node_modules/react-dom/cjs/react-dom.development.js:22380:12)
at act (node_modules/react-dom/cjs/react-dom-test-utils.development.js:1042:14)
at Object.<anonymous> (src/useName.test.ts:19:5)
at TestScheduler.scheduleTests (node_modules/#jest/core/build/TestScheduler.js:333:13)
at runJest (node_modules/#jest/core/build/runJest.js:404:19)
Test Suites: 1 failed, 1 total
Tests: 1 failed, 1 total
Snapshots: 0 total
Time: 0.32 s, estimated 1 s
Ran all test suites.
Is this possible, and am I doing it the right way?
You should test the returned state instead of the implementation detail(setState). Mock may destroy the functionality of setState. This causes the test case to pass, but the code under test will fail at the actual run time. And mock also make the test vulnerable, when your implementation details change, your test cases have to change accordingly such as mock the new object.
I only test if the interface is satisfied, no matter how the implementation details change, right
useName.ts:
import { useState } from 'react';
export const useName = () => {
const [name, setState] = useState('');
const setName = (firstName: string, lastName: string) => setState([firstName, lastName].join(' '));
return { name, setName };
};
useName.test.ts:
import { renderHook, act } from '#testing-library/react-hooks';
import { useName } from './useName';
describe('70381825', () => {
test('should pass', () => {
const { result } = renderHook(() => {
console.count('render');
return useName();
});
expect(result.current.name).toBe('');
act(() => {
result.current.setName('Kashif', 'Nazar');
});
expect(result.current.name).toBe('Kashif Nazar');
act(() => {
result.current.setName('a', 'b');
});
});
});
Test result:
PASS examples/70381825/useName.test.ts
70381825 - mock way
○ skipped should pass
70381825
✓ should pass (29 ms)
console.count
render: 1
at examples/70381825/useName.test.ts:31:15
console.count
render: 2
at examples/70381825/useName.test.ts:31:15
console.count
render: 3
at examples/70381825/useName.test.ts:31:15
Test Suites: 1 passed, 1 total
Tests: 1 skipped, 1 passed, 2 total
Snapshots: 0 total
Time: 1.251 s, estimated 8 s
Now, if you insist to use a mock way. You should only mock useState hook of React. jest.mock('react') will create mocks for all methods, properties, and functions exported by React, and this will break their functions.
E.g.
useName.test.ts:
import { renderHook, act } from '#testing-library/react-hooks';
import { useName } from './useName';
import React from 'react';
jest.mock('react', () => {
return { ...(jest.requireActual('react') as any), useState: jest.fn() };
});
describe('70381825 - mock way', () => {
test('should pass', () => {
const setState = jest.fn();
(React.useState as jest.MockedFunction<typeof React.useState>).mockReturnValue(['ignore', setState]);
const { result } = renderHook(() => {
console.count('render');
return useName();
});
act(() => {
result.current.setName('a', 'b');
});
expect(result.current.name).toBe('ignore');
expect(setState).toBeCalled();
act(() => {
result.current.setName('c', 'd');
});
});
});
Test result:
PASS examples/70381825/useName.test.ts (7.885 s)
70381825 - mock way
✓ should pass (29 ms)
70381825
○ skipped should pass
console.count
render: 1
at examples/70381825/useName.test.ts:14:15
Test Suites: 1 passed, 1 total
Tests: 1 skipped, 1 passed, 2 total
Snapshots: 0 total
Time: 8.487 s
Ok. Do you know why the mock way only renders one time and the other way renders three times when we call the setName? As I said earlier.

Not getting expected result from .toHaveBeenCalledTimes() in react-testing-library

Anyhow, trying to test if a function has been called after its fired. The fireEvent is working as I get a console.log from that function. But the .toHaveBeenCalledTimes(1) returns 0. What have i missed?
If I have the handleLoginSubmit function in the parent and pass it as a prop down to the child and in the test everything passes. But if it's in the same component it fails. Using typescript if that has any meaning.
This is tested
import React, { FC } from 'react';
type Event = React.FormEvent<HTMLFormElement>;
interface Login {
handleLoginSubmit?: (event: Event) => React.ReactNode;
}
const Login: FC<Login> = () => {
const handleLoginSubmit = (_event: Event) => {
console.log('Firing' ); // This is logged
};
return (
<form data-testid='form' onSubmit={(event) => handleLoginSubmit(event)}>
<input data-testid='email'/>
<input data-testid='password'/>
<button data-testid='login-button'>login</button>
</form>
);
};
export default Login;
My test for submiting
it('should handle ClickEvents', () => {
const handleLoginSubmit = jest.fn();
const { getByTestId } = render(<Login/>);
expect(getByTestId('login-button')).toBeTruthy();
fireEvent.submit(getByTestId('form'));
expect(handleLoginSubmit).toHaveBeenCalledTimes(1);
});
Error message
● Login page › should handle ClickEvents
expect(jest.fn()).toHaveBeenCalledTimes(expected)
Expected number of calls: 1
Received number of calls: 0
32 | fireEvent.submit(getByTestId('form'));
33 |
> 34 | expect(handleLoginSubmit).toHaveBeenCalledTimes(1);
| ^
35 |
36 | });
37 | });
at Object.it (__tests__/components/Login.test.tsx:34:31)
You can't assert if the handleLoginSubmit function is to be called directly. Since it's defined in the private scope of Login SFC. You can't mock or spy on this function because you can't access it. So, you need to test it indirectly. Since you are using console.log in this function, we can spy console.log. If it's been called, that means the handleLoginSubmit function has been called.
E.g.
index.tsx:
import React, { FC } from "react";
type Event = React.FormEvent<HTMLFormElement>;
interface Login {
handleLoginSubmit?: (event: Event) => React.ReactNode;
}
const Login: FC<Login> = () => {
const handleLoginSubmit = (_event: Event) => {
console.log("Firing");
};
return (
<form data-testid="form" onSubmit={event => handleLoginSubmit(event)}>
<input data-testid="email" />
<input data-testid="password" />
<button data-testid="login-button">login</button>
</form>
);
};
export default Login;
index.spec.tsx:
import { render, fireEvent } from "#testing-library/react";
import Login from "./";
import React from "react";
it("should handle ClickEvents", () => {
const logSpy = jest.spyOn(console, "log");
const { getByTestId } = render(<Login />);
expect(getByTestId("login-button")).toBeTruthy();
fireEvent.submit(getByTestId("form"));
expect(logSpy).toHaveBeenCalledTimes(1);
});
Unit test result with 100% coverage:
PASS src/stackoverflow/59162138/index.spec.tsx
✓ should handle ClickEvents (42ms)
console.log node_modules/jest-mock/build/index.js:860
Firing
-----------|----------|----------|----------|----------|-------------------|
File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s |
-----------|----------|----------|----------|----------|-------------------|
All files | 100 | 100 | 100 | 100 | |
index.tsx | 100 | 100 | 100 | 100 | |
-----------|----------|----------|----------|----------|-------------------|
Test Suites: 1 passed, 1 total
Tests: 1 passed, 1 total
Snapshots: 0 total
Time: 3.987s, estimated 9s
Source code: https://github.com/mrdulin/jest-codelab/tree/master/src/stackoverflow/59162138

Resources