Skip to content
Prev Previous commit
Next Next commit
remove more relative paths
  • Loading branch information
MatanBobi committed Nov 12, 2020
commit 16bbc63fdaf4aa32ac6d006af4e376b09fba48f6
2 changes: 1 addition & 1 deletion docs/example-react-intl.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@ You have two options:

To test our translated component we can create a custom `render` function using
the `wrapper` option as explained in the
[setup](./react-testing-library/setup.mdx) page.
[setup](react-testing-library/setup.mdx) page.
Our custom `render` function can look like this:

```jsx
Expand Down
4 changes: 2 additions & 2 deletions docs/marko-testing-library/intro.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -49,8 +49,8 @@ when a real user uses it.
**What this library is not**:

1. A test runner or framework
2. Specific to a testing framework, you can [use it with Jest](./setup.mdx#jest),
[mocha](./setup.mdx#mocha), or other test runners.
2. Specific to a testing framework, you can [use it with Jest](setup.mdx#jest),
[mocha](setup.mdx#mocha), or other test runners.

> NOTE: This library is built on top of
> [`DOM Testing Library`](dom-testing-library/intro.mdx) which is where most of
Expand Down
2 changes: 1 addition & 1 deletion docs/react-testing-library/api.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -119,7 +119,7 @@ See [helpers](dom-testing-library/api-helpers.mdx) for guidance on using utility
functions to create custom queries.

Custom queries can also be added globally by following the
[custom render guide](./setup.mdx#custom-render).
[custom render guide](setup.mdx#custom-render).

## `render` Result

Expand Down
2 changes: 1 addition & 1 deletion docs/react-testing-library/example-intro.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -131,7 +131,7 @@ test('handlers server error', async () => {

### Arrange

The [`render`](./api.mdx#render) method renders a React element into the DOM.
The [`render`](api.mdx#render) method renders a React element into the DOM.

```jsx
render(<Fetch url="/greeting" />)
Expand Down
4 changes: 2 additions & 2 deletions docs/react-testing-library/intro.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -55,14 +55,14 @@ This library is a replacement for [Enzyme](http://airbnb.io/enzyme/). While you
_can_ follow these guidelines using Enzyme itself, enforcing this is harder
because of all the extra utilities that Enzyme provides (utilities which
facilitate testing implementation details). Read more about this in
[the FAQ](./faq).
[the FAQ](faq).

**What this library is not**:

1. A test runner or framework
2. Specific to a testing framework (though we recommend Jest as our preference,
the library works with any framework. See
[Using Without Jest](./setup.mdx#using-without-jest))
[Using Without Jest](setup.mdx#using-without-jest))

> NOTE: This library is built on top of
> [`DOM Testing Library`](dom-testing-library/intro.mdx) which is where most of
Expand Down
4 changes: 2 additions & 2 deletions docs/react-testing-library/migrate-from-enzyme.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ work can be done collaboratively and spread over some time.
## Install React Testing Library

You can check
[this page](./setup.mdx) for
[this page](setup.mdx) for
the complete installation and setup guide.

Here is what you should do, first you need to install the React Testing Library:
Expand Down Expand Up @@ -371,4 +371,4 @@ Then make your test do that.
Generally, you should avoid mocking out components. However, if you need to,
then it's pretty trivial using
[Jest's mocking](https://jestjs.io/docs/en/manual-mocks.html) feature. (see our
[FAQ](./faq.mdx))
[FAQ](faq.mdx))