I have a unit test that uses spyOn method from jest.

import React from 'react';
import expect from 'jest-matchers';
import PointsAwardingPage from '../PointsAwardingPage';
import PointsAwardingForm from '../children/PointsAwardingForm';
import { shallow } from 'enzyme';

it("should call change method in form", () => {
  // given
  spyOn(PointsAwardingPage.prototype, 'change').and.callThrough();
  const form = shallow(<PointsAwardingPage />).find('PointsAwardingForm');

  // when
  form.props().onChange();

  // then
  expect(PointsAwardingPage.prototype.change).toHaveBeenCalled();
});

Everything works well. However, I see the following eslint error message regarding the spyOn function call.

spyOn is not defined (no-undef).

Which import statement can I use in order to get rid of this error?

I have a unit test that uses spyOn method from jest.

import React from 'react';
import expect from 'jest-matchers';
import PointsAwardingPage from '../PointsAwardingPage';
import PointsAwardingForm from '../children/PointsAwardingForm';
import { shallow } from 'enzyme';

it("should call change method in form", () => {
  // given
  spyOn(PointsAwardingPage.prototype, 'change').and.callThrough();
  const form = shallow(<PointsAwardingPage />).find('PointsAwardingForm');

  // when
  form.props().onChange();

  // then
  expect(PointsAwardingPage.prototype.change).toHaveBeenCalled();
});

Everything works well. However, I see the following eslint error message regarding the spyOn function call.

spyOn is not defined (no-undef).

Which import statement can I use in order to get rid of this error?

• javascript
• unit-testing
• jestjs
• eslint

Share Follow asked Sep 28, 2017 at 3:32 alayoralayor 5,05577 gold badges2929 silver badges5151 bronze badges

Add a ment  | 

2 Answers 2

Sorted by: Reset to default 11

Although a global ment is a valid solution, I believe you could simply use jest.spyOn() instead.

Don't forget to define jest in your .eslintrc:

"env": {
    "jest": true
}

That's because spyOn is provided by the test environment - in your case Jest - thus it's not defined by you.

ESLint looks for definitions in your code only.

An easy and safe way to get rid of it is to place a ment /*global spyOn*/ at the top of your test file, which tells ESLint that you have defined it, without actually doing so.