I have some unit tests set up, testing with enzyme's shallow method with a jsdom configuration. This has been working well until I have run into a ponent where I am using window.addEventListener. The unit tests is now giving back the error of
TypeError: window.addEventListener is not a function
I have my test helpers set up for JSdom like so
import jsdom from 'jsdom';
...
global.document = jsdom.jsdom('<!doctype html><html><body></body></html>');
global.window = document.defaultView;
global.navigator = {userAgent: 'node.js'};
this was working fine, then I upgraded to enzyme 3.x, and now I am getting this error.
I am wondering do i need to manually mock the addEventListener now, or is there something I am doing wrong to access this.
I have some unit tests set up, testing with enzyme's shallow method with a jsdom configuration. This has been working well until I have run into a ponent where I am using window.addEventListener. The unit tests is now giving back the error of
TypeError: window.addEventListener is not a function
I have my test helpers set up for JSdom like so
import jsdom from 'jsdom';
...
global.document = jsdom.jsdom('<!doctype html><html><body></body></html>');
global.window = document.defaultView;
global.navigator = {userAgent: 'node.js'};
this was working fine, then I upgraded to enzyme 3.x, and now I am getting this error.
I am wondering do i need to manually mock the addEventListener now, or is there something I am doing wrong to access this.
Share Improve this question asked Dec 4, 2017 at 16:19 ajmajmajmaajmajmajma 14.2k25 gold badges83 silver badges138 bronze badges3 Answers
Reset to default 6//in test file ...
it("should render KeyStrokeHandler", () => {
// Set-up event listener mock
const map = {};
window.addEventListener = jest.fn((event, callback) => {
map[event] = callback;
});
// Mount ponent that has set callback for keydown event
const wrapper = mount(<KeyStrokeHandler />);
// Trigger keydown event
map.keydown({ key: 'Enter' });
});
...
I had the same issue in trying to check if the addEventListener has been called in ponentDidMount this seems to work for me (jest, enzyme)
//ponent
ponentDidMount(){
document.addEventListener("keydown", this.handleKeydownOnSearch, false);
}
....
//in test file ...
it("on ponent mount we set the keydown listener", () => {
global.document.addEventListener = jest.fn();
wrapper = shallow(<ItemSearch />);
expect(global.document.addEventListener).toHaveBeenCalled();
});
...
I mock my document just like you do, and then if I need to use addEventListener() in a test, I just mock it in a beforeEach
beforeEach(() => {
document = {
...document,
addEventListener: () => { },
removeEventListener: () => { }
}
})