docs(vitest): document buildPagesASSETSBinding()

Author: edmundhung

src/content/docs/workers/testing/vitest-integration/configuration.mdx

@@ -46,25 +46,117 @@ Custom Vitest `environment`s or `runner`s are not supported when using the Worke
 
 :::
 
-## Functions
+## APIs
 
-The following functions are exported from the `@cloudflare/vitest-pool-workers/config` module.
+The following APIs are exported from the `@cloudflare/vitest-pool-workers/config` module.
 
+### `defineWorkersConfig(options)`
 
+Ensures Vitest is configured to use the Workers integration with the correct module resolution settings, and provides type checking for [WorkersPoolOptions](#workerspooloptions). This should be used in place of the [`defineConfig()`](https://vitest.dev/config/file.html) function from Vitest. The `defineWorkersConfig()` function also accepts a `Promise` of `options`, or an optionally-`async` function returning `options`.
 
-* `defineWorkersConfig(options:UserConfig & { test?: { poolOptions?: { workers?: WorkersPoolOptions | ((ctx: WorkerPoolOptionsContext) => Awaitable\<WorkersPoolOptions>) } } })`
+```ts
+import { defineWorkersConfig } from "@cloudflare/vitest-pool-workers/config";
 
-  * Ensures Vitest is configured to use the Workers integration with the correct module resolution settings, and provides type checking for `WorkersPoolOptions`. This should be used in place of the [`defineConfig()`](https://vitest.dev/config/file.html) function from Vitest. The `defineWorkersConfig()` function also accepts a `Promise` of `options`, or an optionally-`async` function returning `options`.
+export default defineWorkersConfig({
+  test: {
+    poolOptions: {
+      workers: {
+        // ...
+      },
+    },
+  },
+});
+```
 
-* `defineWorkersProject(options:UserWorkspaceConfig & { test?: { poolOptions?: { workers?: WorkersPoolOptions | ((ctx: WorkerPoolOptionsContext) => Awaitable\<WorkersPoolOptions>) } } })`
+### `defineWorkersProject(options)`
 
-  * Ensures Vitest is configured to use the Workers integration with the correct module resolution settings, and provides type checking for `WorkersPoolOptions`. This should be used in place of the [`defineProject()`](https://vitest.dev/guide/workspace) function from Vitest. The `defineWorkersProject()` function also accepts a `Promise` of `options`, or an optionally-`async` function returning `options`.
+Ensures Vitest is configured to use the Workers integration with the correct module resolution settings, and provides type checking for [WorkersPoolOptions](#workerspooloptions) similar to `defineWorkersConfig`, except this should be used in place of the [`defineProject()`](https://vitest.dev/guide/workspace) function from Vitest. The `defineWorkersProject()` function also accepts a `Promise` of `options`, or an optionally-`async` function returning `options`.
 
-* `readD1Migrations(migrationsPath:string)`: `D1Migration[]`
+```ts
+import { defineWorkspace, defineProject } from "vitest/config";
+import { defineWorkersProject } from "@cloudflare/vitest-pool-workers/config";
+
+const workspace = defineWorkspace([
+	defineWorkersProject({
+		test: {
+			name: "Workers",
+			include: ["**/*.worker.test.ts"],
+			poolOptions: {
+				workers: {
+					// ...
+				},
+			},
+		},
+	}),
+
+	// ...
+]);
+
+export default workspace;
+```
+
+### `buildPagesASSETSBinding(assetsPath)`
+
+Creates a Pages ASSETS binding that serves files insides the `assetsPath`. This is required if you uses `createPagesEventContext()` to test your Pages function. Refer to the [Pages recipe](/workers/testing/vitest-integration/recipes) for an example on testing Pages function.
 
-  * Reads all [D1 migrations](/d1/reference/migrations/) stored at `migrationsPath` and returns them ordered by migration number. Each migration will have its contents split into an array of individual SQL queries. Call the [`applyD1Migrations()`](/workers/testing/vitest-integration/test-apis/#d1) function inside a test or [setup file](https://vitest.dev/config/#setupfiles) to apply migrations. Refer to the [D1 recipe](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/d1) for an example project using migrations.
+```ts
+import path from "node:path";
+import {
+	buildPagesASSETSBinding,
+	defineWorkersProject,
+} from "@cloudflare/vitest-pool-workers/config";
+
+export default defineWorkersProject(async () => {
+	const assetsPath = path.join(__dirname, "public");
+
+	return {
+		test: {
+			poolOptions: {
+				workers: {
+					miniflare: {
+						serviceBindings: {
+							ASSETS: await buildPagesASSETSBinding(assetsPath),
+						},
+					},
+				},
+			},
+		},
+	};
+});
 
+```
 
+### `readD1Migrations(migrationsPath)`
+
+Reads all [D1 migrations](/d1/reference/migrations/) stored at `migrationsPath` and returns them ordered by migration number. Each migration will have its contents split into an array of individual SQL queries. Call the [`applyD1Migrations()`](/workers/testing/vitest-integration/test-apis/#d1) function inside a test or [setup file](https://vitest.dev/config/#setupfiles) to apply migrations. Refer to the [D1 recipe](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/d1) for an example project using migrations.
+
+```ts
+import path from "node:path";
+import {
+	defineWorkersProject,
+	readD1Migrations,
+} from "@cloudflare/vitest-pool-workers/config";
+
+export default defineWorkersProject(async () => {
+	// Read all migrations in the `migrations` directory
+	const migrationsPath = path.join(__dirname, "migrations");
+	const migrations = await readD1Migrations(migrationsPath);
+
+	return {
+		test: {
+			setupFiles: ["./test/apply-migrations.ts"],
+			poolOptions: {
+				workers: {
+					miniflare: {
+						// Add a test-only binding for migrations, so we can apply them in a setup file
+						bindings: { TEST_MIGRATIONS: migrations },
+					},
+				},
+			},
+		},
+	};
+});
+```
 
 ## `WorkersPoolOptions`
 

src/content/docs/workers/testing/vitest-integration/recipes.mdx

@@ -10,9 +10,10 @@ description: Examples that demonstrate how to write unit tests and integration
 
 Recipes are examples that help demonstrate how to write unit tests and integration tests for Workers projects using the [`@cloudflare/vitest-pool-workers`](https://www.npmjs.com/package/@cloudflare/vitest-pool-workers) package.
 
-- [Basic unit and integration tests using `SELF`](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/basics-unit-integration-self)
+- [Basic unit and integration tests for Workers using `SELF`](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/basics-unit-integration-self)
+- [Basic unit and integration tests for Pages function using `SELF`](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/pages-functions-unit-integration-self)
 - [Basic integration tests using an auxiliary Worker](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/basics-integration-auxiliary)
-- [Basic integration test for a Worker with static assets](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/workers-assets)
+- [Basic integration test for Workers with static assets](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/workers-assets)
 - [Isolated tests using KV, R2 and the Cache API](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/kv-r2-caches)
 - [Isolated tests using D1 with migrations](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/d1)
 - [Isolated tests using Durable Objects with direct access](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/durable-objects)