From bb6b6e254ddc525edf17b5cad57c2b36a3e7ab7a Mon Sep 17 00:00:00 2001
From: Ryota Watanabe <43837308+wattanx@users.noreply.github.com>
Date: Sun, 13 Oct 2024 05:31:29 +0900
Subject: [PATCH] docs: add a description for `.env.test` (#29398)

---
 docs/1.getting-started/11.testing.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/1.getting-started/11.testing.md b/docs/1.getting-started/11.testing.md
index dce433a768..defd522f92 100644
--- a/docs/1.getting-started/11.testing.md
+++ b/docs/1.getting-started/11.testing.md
@@ -68,6 +68,10 @@ When importing `@nuxt/test-utils` in your vitest config, It is necessary to have
 > ie. `vitest.config.m{ts,js}`.
 ::
 
+::tip
+It is possible to set environment variables for testing by using the `.env.test` file.
+::
+
 ### Using a Nuxt Runtime Environment
 
 By default, `@nuxt/test-utils` will not change your default Vitest environment, so you can do fine-grained opt-in and run Nuxt tests together with other unit tests.