Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

(docs): clarify clear vs reset mocks #3579

Merged
merged 1 commit into from
May 17, 2017
Merged

(docs): clarify clear vs reset mocks #3579

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/en/Configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -261,7 +261,7 @@ This example configuration will run Jest in the root directory as well as in eve
### `clearMocks` [boolean]
Default: `false`

Automatically clear mock calls and instances between every test. Equivalent to calling `jest.clearAllMocks()` between each test.
Automatically clear mock calls and instances between every test. Equivalent to calling `jest.clearAllMocks()` between each test. This does not remove any mock implementation that may have been provided.

### `reporters` [array<moduleName | [moduleName, options]>]
Default: `undefined`
Expand Down Expand Up @@ -339,7 +339,7 @@ For the full list of methods and argument types see `Reporter` type in [types/Te
### `resetMocks` [boolean]
Default: `false`

Automatically reset mock state between every test. Equivalent to calling `jest.resetAllMocks()` between each test.
Automatically reset mock state between every test. Equivalent to calling `jest.resetAllMocks()` between each test. This will lead to any mocks having their fake implementations removed but does not restore their initial implementation.

### `resetModules` [boolean]
Default: `false`
Expand Down