Unverified Commit 315a9078 authored by 루밀LuMir's avatar 루밀LuMir Committed by GitHub

docs(typo): fix typos in `08-testing/index.mdx` (#72057)

## 📚 Improving Documentation

Hello, I've fixed  `testing` to `Testing`. (lowercase to uppercase)


![image](https://github.com/user-attachments/assets/3d3198cf-e750-4957-b436-1e964d6976e9)

In other documents, `T` is always uppercase as shown in the screenshot
above.
Co-authored-by: 's avatarJJ Kasper <jj@jjsweb.site>
parent fd438464
...@@ -7,11 +7,11 @@ In React and Next.js, there are a few different types of tests you can write, ea ...@@ -7,11 +7,11 @@ In React and Next.js, there are a few different types of tests you can write, ea
## Types of tests ## Types of tests
- **Unit testing** involves testing individual units (or blocks of code) in isolation. In React, a unit can be a single function, hook, or component. - **Unit Testing** involves testing individual units (or blocks of code) in isolation. In React, a unit can be a single function, hook, or component.
- **Component testing** is a more focused version of unit testing where the primary subject of the tests is React components. This may involve testing how components are rendered, their interaction with props, and their behavior in response to user events. - **Component Testing** is a more focused version of unit testing where the primary subject of the tests is React components. This may involve testing how components are rendered, their interaction with props, and their behavior in response to user events.
- **Integration testing** involves testing how multiple units work together. This can be a combination of components, hooks, and functions. - **Integration Testing** involves testing how multiple units work together. This can be a combination of components, hooks, and functions.
- **End-to-End (E2E) Testing** involves testing user flows in an environment that simulates real user scenarios, like the browser. This means testing specific tasks (e.g. signup flow) in a production-like environment. - **End-to-End (E2E) Testing** involves testing user flows in an environment that simulates real user scenarios, like the browser. This means testing specific tasks (e.g. signup flow) in a production-like environment.
- **Snapshot testing** involves capturing the rendered output of a component and saving it to a snapshot file. When tests run, the current rendered output of the component is compared against the saved snapshot. Changes in the snapshot are used to indicate unexpected changes in behavior. - **Snapshot Testing** involves capturing the rendered output of a component and saving it to a snapshot file. When tests run, the current rendered output of the component is compared against the saved snapshot. Changes in the snapshot are used to indicate unexpected changes in behavior.
<AppOnly> <AppOnly>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment