From 1006a4fac2808a9baab3a6b596cf1262fe6f9acd Mon Sep 17 00:00:00 2001
From: Henrique Fonseca <60244227+Tamicktom@users.noreply.github.com>
Date: Fri, 28 Nov 2025 04:15:34 -0300
Subject: [PATCH] =?UTF-8?q?Fix=20incorrect=20file=20name=20in=20React=20co?=
 =?UTF-8?q?mponent=20test=20example=20=F0=9F=8C=9F=20(#25167)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

# What does this PR do?

Nyaa~ This PR fixes a small mistake in the documentation where the code
block for a React component test example was using the wrong filename!
(；ω；)💦

It was previously labeled as `matchers.d.ts`, but it should be something
like `myComponent.test.tsx` to properly reflect a test file for a React
component using `@testing-library/react`. 🧁✨

This makes the example clearer and more accurate for developers using
Bun to test their React components~! 💻🌸💕

# How did you verify your code works?

It's just docs, one single line 🥺

Pwease review and merge it when you can, senpai~~! UwU 🌈🫧
---
 docs/guides/test/testing-library.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/guides/test/testing-library.mdx b/docs/guides/test/testing-library.mdx
index 7e4ed0a440..503490f194 100644
--- a/docs/guides/test/testing-library.mdx
+++ b/docs/guides/test/testing-library.mdx
@@ -76,7 +76,7 @@ declare module "bun:test" {
 
 You should now be able to use Testing Library in your tests
 
-```ts matchers.d.ts icon="/icons/typescript.svg"
+```tsx myComponent.test.tsx icon="/icons/typescript.svg"
 import { test, expect } from "bun:test";
 import { screen, render } from "@testing-library/react";
 import { MyComponent } from "./myComponent";