Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
sheremet-va authored Aug 14, 2024
1 parent 1ec6d02 commit b9c3e0f
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ test('counter button increments the count', async () => {
> [!NOTE]
> This library doesn't expose or use React's `act`. Instead, you should use Vitest's locators and `expect.element` API that have [retry-ability mechanism](https://vitest.dev/guide/browser/assertion-api) baked in.
`vitest-browser-react` also automatically injects `render` and `cleanup` methods on the `page`. Example:
`vitest-browser-react` also automatically injects `render` method on the `page`. Example:

```ts
// vitest.config.ts
Expand All @@ -46,7 +46,7 @@ test('counter button increments the count', async () => {
})
```

Unlike `@testing-library/react`, `vitest-browser-react` cleans up the component before the test starts instead of after, so you can see the rendered result in your UI. To avoid auto-cleanup, import the `render` function from `vitest-browser-vue/pure`.
Unlike `@testing-library/react`, `vitest-browser-react` cleans up the component before the test starts instead of after, so you can see the rendered result in your UI. To avoid auto-cleanup, import the `render` function from `vitest-browser-react/pure`.

## Special thanks

Expand Down

0 comments on commit b9c3e0f

Please sign in to comment.