chore: apply review suggestions

Author: ianlet

docs/qwik-testing-library/api.mdx

@@ -14,14 +14,20 @@ sidebar_label: API
 
 ## `render`
 
-Render your component to the DOM with Qwik. By default, the component will be
-rendered into a `<host>` appended to `document.body`.
+Render your component to the DOM with Qwik. By default, when no options are
+provided, the component will be rendered into a `<host>` appended to
+`document.body`.
 
 ```tsx
 import {render} from '@noma.to/qwik-testing-library'
+import {MockProvider} from './MockProvider'
 import {MyComponent} from './MyComponent'
 
-const result = await render(<MyComponent />, renderOptions)
+const result = await render(<MyComponent />, {
+  baseElement: document.body,
+  container: document.createElement('host'),
+  wrapper: MockProvider,
+})
 ```
 
 ### Render Options

docs/qwik-testing-library/example.mdx

@@ -35,11 +35,12 @@ describe('<Counter />', () => {
     // retrieve the 'increment count' button
     const incrementBtn = screen.getByRole('button', {name: /increment count/})
     // click the button twice
-    await userEvent.click(incrementBtn)
-    await userEvent.click(incrementBtn)
+    const user = userEvent.setup()
+    await user.click(incrementBtn)
+    await user.click(incrementBtn)
 
     // assert that the counter is now 2
-    await waitFor(() => expect(screen.getByText(/count:2/)).toBeInTheDocument())
+    expect(await screen.findByText(/count:2/)).toBeInTheDocument()
   })
 })
 ```
@@ -55,6 +56,8 @@ We're happy to discuss it on [Discord][discord], but we consider this failure to
 be a good thing: your components should be tested in isolation, so you will be
 forced to mock your server functions.
 
+[discord]: https://qwik.dev/chat
+
 Here is an example of how to test a component that uses `server$` calls:
 
 ```ts title="~/server/blog-post.ts"
@@ -85,9 +88,7 @@ describe('<LatestPostList />', () => {
   it('should render the latest posts', async () => {
     await render(<LatestPostList />)
 
-    await waitFor(() =>
-      expect(screen.queryAllByRole('listitem')).toHaveLength(2),
-    )
+    expect(await screen.findAllByRole('listitem')).toHaveLength(2)
   })
 })
 ```
@@ -97,5 +98,5 @@ being named as `getLatestPosts$`. This is caused by the Qwik optimizer renaming
 it to `Qrl`. So, we need to mock the `Qrl` function instead of the original `$`
 one.
 
-If your `server$` function doesn't end with `$`, the Qwik optimizer might not
-rename it to `Qrl`.
+If your function doesn't end with `$`, the Qwik optimizer will not rename it to
+`Qrl`.

docs/qwik-testing-library/setup.mdx

@@ -20,10 +20,11 @@ This module is distributed via [npm][npm] which is bundled with [node][node] and
 should be installed as one of your project's `devDependencies`:
 
 ```bash npm2yarn
-npm install --save-dev @noma.to/qwik-testing-library
+npm install --save-dev @noma.to/qwik-testing-library @testing-library/dom
 ```
 
-This library supports `qwik` versions `1.7.2` and above.
+This library supports `qwik` versions `1.7.2` and above and
+`@testing-library/dom` versions `10.1.0` and above.
 
 You may also be interested in installing `@testing-library/jest-dom` and
 `@testing-library/user-event` so you can use [the custom jest
@@ -48,8 +49,8 @@ npm install --save-dev jsdom
 
 ## Vitest Configuration
 
-We recommend using `@noma.to/qwik-testing-library` with [Vitest][] as your test
-runner.
+We recommend using `@noma.to/qwik-testing-library` with [Vitest][vitest] as your
+test runner.
 
 If you haven't done so already, add vitest to your project using Qwik CLI:
 
@@ -108,26 +109,31 @@ create it:
 Then, create the `vitest.setup.ts` file:
 
 ```ts title="vitest.setup.ts"
-import {afterEach} from 'vitest'
+// Configure DOM matchers to work in Vitest
 import '@testing-library/jest-dom/vitest'
 
 // This has to run before qdev.ts loads. `beforeAll` is too late
 globalThis.qTest = false // Forces Qwik to run as if it was in a Browser
 globalThis.qRuntimeQrl = true
 globalThis.qDev = true
 globalThis.qInspector = false
-
-afterEach(async () => {
-  const {cleanup} = await import('@noma.to/qwik-testing-library')
-  cleanup()
-})
 ```
 
-This setup will make sure that Qwik is properly configured and that everything
-gets cleaned after each test.
+This setup will make sure that Qwik is properly configured. It also loads
+`@testing-library/jest-dom/vitest` in your test runner so you can use matchers
+like `expect(...).toBeInTheDocument()`.
+
+By default, Qwik Testing Library cleans everything up automatically for you. You
+can opt out of this by setting the environment variable `QTL_SKIP_AUTO_CLEANUP`
+to `true`. Then in your tests, you can call the `cleanup` function when needed.
+For example:
 
-Additionally, it loads `@testing-library/jest-dom/vitest` in your test runner so
-you can use matchers like `expect(...).toBeInTheDocument()`.
+```ts
+import {cleanup} from '@noma.to/qwik-testing-library'
+import {afterEach} from 'vitest'
+
+afterEach(cleanup)
+```
 
 Now, edit your `tsconfig.json` to declare the following global types: