Skip to content

Commit

Permalink
Update ManualMocks.md (#8781)
Browse files Browse the repository at this point in the history
  • Loading branch information
shopped authored and SimenB committed Aug 4, 2019
1 parent 2a004bf commit 2eea09f
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion docs/ManualMocks.md
Expand Up @@ -9,7 +9,7 @@ Manual mocks are used to stub out functionality with mock data. For example, ins

Manual mocks are defined by writing a module in a `__mocks__/` subdirectory immediately adjacent to the module. For example, to mock a module called `user` in the `models` directory, create a file called `user.js` and put it in the `models/__mocks__` directory. Note that the `__mocks__` folder is case-sensitive, so naming the directory `__MOCKS__` will break on some systems.

> When we require that module in our tests, then explicitly calling `jest.mock('./moduleName')` is **required**.
> When we require that module in our tests, explicitly calling `jest.mock('./moduleName')` is **required**.
## Mocking Node modules

Expand Down
2 changes: 1 addition & 1 deletion website/versioned_docs/version-22.x/ManualMocks.md
Expand Up @@ -10,7 +10,7 @@ Manual mocks are used to stub out functionality with mock data. For example, ins

Manual mocks are defined by writing a module in a `__mocks__/` subdirectory immediately adjacent to the module. For example, to mock a module called `user` in the `models` directory, create a file called `user.js` and put it in the `models/__mocks__` directory. Note that the `__mocks__` folder is case-sensitive, so naming the directory `__MOCKS__` will break on some systems.

> When we require that module in our tests, then explicitly calling `jest.mock('./moduleName')` is **required**.
> When we require that module in our tests, explicitly calling `jest.mock('./moduleName')` is **required**.
## Mocking Node modules

Expand Down
2 changes: 1 addition & 1 deletion website/versioned_docs/version-23.x/ManualMocks.md
Expand Up @@ -10,7 +10,7 @@ Manual mocks are used to stub out functionality with mock data. For example, ins

Manual mocks are defined by writing a module in a `__mocks__/` subdirectory immediately adjacent to the module. For example, to mock a module called `user` in the `models` directory, create a file called `user.js` and put it in the `models/__mocks__` directory. Note that the `__mocks__` folder is case-sensitive, so naming the directory `__MOCKS__` will break on some systems.

> When we require that module in our tests, then explicitly calling `jest.mock('./moduleName')` is **required**.
> When we require that module in our tests, explicitly calling `jest.mock('./moduleName')` is **required**.
## Mocking Node modules

Expand Down

0 comments on commit 2eea09f

Please sign in to comment.