pr feedback

Author: emily-shen

src/content/docs/workers/testing/index.mdx

@@ -7,16 +7,16 @@ sidebar:
 
 import { Render, LinkButton } from "~/components";
 
-The Workers platform has a variety of ways to test your applications, depending on your requirements. We recommend using the [Vitest integration](/workers/testing/vitest-integration), which allows for unit testing individual functions within your Worker.
+The Workers platform has a variety of ways to test your applications, depending on your requirements. We recommend using the [Vitest integration](/workers/testing/vitest-integration), which allows you to run tests to _inside_ the Workers runtime, and unit test individual functions within your Worker.
 
 <LinkButton href="/workers/testing/vitest-integration/get-started/write-your-first-test/">
 	Get started with Vitest
 </LinkButton>
 
-However, if you don't use Vitest, both [Miniflare's API](/workers/testing/miniflare/writing-tests) and the [`unstable_startWorker()`](/workers/wrangler/api/#unstable_startworker) API provide options for testing your Worker in any testing framework.
-
 ## Testing comparison matrix
 
+However, if you don't use Vitest, both [Miniflare's API](/workers/testing/miniflare/writing-tests) and the [`unstable_startWorker()`](/workers/wrangler/api/#unstable_startworker) API provide options for testing your Worker in any testing framework.
+
 | Feature                                                                  | [Vitest integration](/workers/testing/vitest-integration) | [`unstable_startWorker()`](/workers/wrangler/api/#unstable_startworker) | [Miniflare's API](/workers/testing/miniflare) |
 | ------------------------------------------------------------------------ | --------------------------------------------------------- | ----------------------------------------------------------------------- | --------------------------------------------- |
 | Unit testing                                                             | ✅                                                        | ❌                                                                      | ❌                                            |

src/content/docs/workers/testing/vitest-integration/get-started/index.mdx

@@ -11,24 +11,4 @@ description: Install and set up the Workers Vitest integration.
 
 import { DirectoryListing } from "~/components";
 
-For most users, Cloudflare recommends using the Workers Vitest integration for testing Workers and [Pages Functions](/pages/functions/) projects. [Vitest](https://vitest.dev/) is a popular JavaScript testing framework featuring a very fast watch mode, Jest compatibility, and out-of-the-box support for TypeScript. In this integration, Cloudflare provides a custom pool that allows your Vitest tests to run _inside_ the Workers runtime.
-
-The Workers Vitest integration:
-
-- Supports both **unit tests** and **integration tests**.
-- Provides direct access to Workers runtime APIs and bindings.
-- Implements isolated per-test storage.
-- Runs tests fully-locally using [Miniflare](https://miniflare.dev/).
-- Leverages Vitest's hot-module reloading for near instant reruns.
-- Provides a declarative interface for mocking outbound requests.
-- Supports projects with multiple Workers.
-
-Get started with one of the available guides:
-
 <DirectoryListing />
-
-:::caution
-
-The Workers Vitest integration does not support testing Workers using the service worker format. [Migrate to the ES modules format](/workers/reference/migrate-to-module-workers/) to use the Workers Vitest integration.
-
-:::

src/content/docs/workers/testing/vitest-integration/get-started/write-your-first-test.mdx

@@ -38,30 +38,27 @@ First, make sure that:
 
 ## Define Vitest configuration
 
-Create a `vitest.config.js` or `vitest.config.ts` file if you do not already have one.
-Then add the following snippet, which uses `defineWorkersConfig` to configure the Workers Vitest integration.
+In your `vitest.config.ts` file, use `defineWorkersConfig` to configure the Workers Vitest integration.
 
-There are two ways to configure the Workers Vitest integration.
+You can use your Worker configuration from your [Wrangler config file](/workers/wrangler/configuration/) by specifying it with `wrangler.configPath`.
 
-1.  If you want to use the same configuration as your Worker, you can simply reference a Wrangler file via `wrangler.configPath`.
+```ts title = vitest.config.ts
+import { defineWorkersConfig } from "@cloudflare/vitest-pool-workers/config";
 
-    ```ts title = vitest.config.ts
-    import { defineWorkersConfig } from "@cloudflare/vitest-pool-workers/config";
-
-    export default defineWorkersConfig({
-    	test: {
-    		poolOptions: {
-    			workers: {
-    				wrangler: { configPath: "./wrangler.toml" },
-    			},
-    		},
-    	},
-    });
-    ```
+export default defineWorkersConfig({
+	test: {
+		poolOptions: {
+			workers: {
+				wrangler: { configPath: "./wrangler.toml" },
+			},
+		},
+	},
+});
+```
 
-2.  You can override configuration using the `miniflare` key.
+You can also override or define additional configuration using the `miniflare` key. This takes precedence over values set in via your Wrangler config.
 
-        For example, this configuration would add a KV namespace `TEST_NAMESPACE` that was only accessed and modified in tests.
+For example, this configuration would add a KV namespace `TEST_NAMESPACE` that was only accessed and modified in tests.
 
         ```js null {6-8}
         export default defineWorkersConfig({
@@ -84,9 +81,12 @@ For a full list of available configuration options, refer to [Configuration](/wo
 
 ## Define types
 
-First make sure you have run [`wrangler types`](/workers/wrangler/commands/), which generates `Env` types based on your Worker's bindings and [runtime types](/workers/languages/typescript/).
+If you are not using Typescript, you can skip this section.
+
+First make sure you have run [`wrangler types`](/workers/wrangler/commands/), which generates [types for the Cloudflare Workers runtime](/workers/languages/typescript/) and an `Env` type based on your Worker's bindings.
 
-If you are using TypeScript, you will need to define types for Cloudflare Workers and `cloudflare:test` to make sure they are detected appropriately. Add a `tsconfig.json` in your tests folder and add `"@cloudflare/vitest-pool-workers"` to your types array.
+Then add a `tsconfig.json` in your tests folder and add `"@cloudflare/vitest-pool-workers"` to your types array to define types for `cloudflare:test`.
+You should also add the output of `wrangler types` to the `include` array so that the types for the Cloudflare Workers runtime are available.
 
 <Details header="Example test/tsconfig.json">
 	```jsonc title="test/tsconfig.json"
@@ -106,7 +106,7 @@ If you are using TypeScript, you will need to define types for Cloudflare Worker
 	```
 </Details>
 
-You also need to define the type of the `env` object that is passed to your tests. Create an `env.d.ts` file in your tests folder, with the following content:
+You also need to define the type of the `env` object that is provided to your tests. Create an `env.d.ts` file in your tests folder, and declare the `ProvidedEnv` interface by extending the `Env` interface that is generated by `wrangler types`.
 
 ```ts title="test/env.d.ts"
 declare module "cloudflare:test" {
@@ -117,9 +117,9 @@ declare module "cloudflare:test" {
 
 If your test bindings differ from the bindings in your Wrangler config, you should type them here in `ProvidedEnv`.
 
-## Write a unit test
+## Writing tests
 
-Given an example Worker like this:
+We will use this simple Worker as an example. It returns a 404 response for the `/404` path and `"Hello World!"` for all other paths.
 
 <TypeScriptExample filename="src/index.ts">
 ```ts
@@ -132,9 +132,12 @@ export default {
 	},
 } satisfies ExportedHandler<Env>;
 ```
+
 </TypeScriptExample>
 
-You might want to add a test like this to check that the Worker response correctly to a request at `/404`.
+### Unit tests
+
+By importing the Worker we can write a unit test for its `fetch` handler.
 
 <TypeScriptExample filename="test/unit.spec.ts">
 	```ts
@@ -168,7 +171,7 @@ You might want to add a test like this to check that the Worker response correct
 
 </TypeScriptExample>
 
-## Write an integration test
+### Integration tests
 
 You can use the SELF fetcher provided by the `cloudflare:test` to write an integration test. This is a service binding to the default export defined in the main Worker. The main Worker runs in the same isolate/context as tests so any global mocks will apply to it too.