Update getting started guide to avoid linter errors

[dandv]

Following the getting started guide and using a linter (e.g. one built into an IDE like WebStorm) will highlight test, expect and toBe in the test file as not defined:

An import should be added for jest.

[thymikee]

If you use ESLint, here's the plugin for you: https://www.npmjs.com/package/eslint-plugin-jest.
It's not a bug in Jest for sure, it's your linter.

[dandv]

Never said this was a bug in Jest, and it's not a linter problem either (I've added and configured eslint-plugin-jest but that didn't help). It's just that any sort of editor that tries to understand your JS code will flag undefined symbols.

In other words, what require statements are necessary so that the test files can be run by node?

$ node index.test.js
[...]
ReferenceError: test is not defined

[thymikee]

test, amongst couple of others, is a global variable injected by Jest. You need to run your tests through jest, not node.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.