feat: 初始化项目并添加多个功能组件

style: 调整UI组件样式和布局

docs: 更新README和添加文档内容

chore: 添加依赖项和配置文件

fix: 修复一些小问题和优化代码

perf: 优化性能相关代码

refactor: 重构部分组件结构

test: 添加测试相关文件

build: 更新构建配置

ci: 添加CI配置文件

content/testing-react-apps.mdx

@@ -0,0 +1,36 @@
+---
+title: "Testing React Applications: A Practical Guide"
+publishedAt: "2024-12-14"
+updatedAt: "2024-12-14"
+author: "John Doe"
+summary: "From unit tests to E2E—learn how to build confidence in your React applications with comprehensive testing."
+image: "https://images.unsplash.com/photo-1516116216624-53e697fedbea?w=800&h=192&fit=crop"
+---
+
+# Testing React Applications: A Practical Guide
+
+Tests are your safety net — they let you refactor with confidence and ship changes without fear. The goal is not “as many tests as possible”; it’s <mark>confidence in the critical paths</mark>.
+
+If your test suite feels slow or fragile, it usually means you’re testing the wrong thing. In practice, you can ignore a lot of “perfect coverage” advice and focus on a few high-signal habits.
+
+## What to test (a simple rule)
+
+- **Unit tests**: small, fast checks for logic and pure functions.
+- **Integration tests**: components + data + user flows (most value per test).
+- **E2E tests**: a few happy-path checks across the whole app.
+
+## High-signal testing habits
+
+- Prefer user-facing assertions (what the user sees/does).
+- Use accessible queries first (roles, labels).
+- Mock at the boundary (network) instead of mocking implementation details.
+
+## Things to avoid
+
+- ~~Testing internal component state~~ when behavior is what matters.
+- ~~Sprinkling test IDs everywhere~~ as a first choice.
+- Overusing snapshots that fail for harmless UI changes.
+
+## Wrap-up
+
+Start small: one integration test for your most important flow, then add unit tests for tricky logic. Over time, your tests become living documentation that helps you move faster.