testing-strategies

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Testing Strategies & Methodologies

测试策略与方法论

Comprehensive testing strategies for building reliable, high-quality software systems.

用于构建可靠、高质量软件系统的综合性测试策略。

Test Pyramid

测试金字塔

        UI/E2E Tests
       /            \
      /              \
   Integration Tests
    /                \
  /                  \
Unit Tests

Unit Tests: Fast, isolated, low-level (60%)
Integration Tests: Component interactions (30%)
E2E Tests: Full system workflows (10%)

        UI/E2E Tests
       /            \
      /              \
   Integration Tests
    /                \
  /                  \
Unit Tests

单元测试：快速、独立、底层（占比60%）
集成测试：组件间交互（占比30%）
E2E测试：完整系统工作流（占比10%）

Testing Types

测试类型

Unit Testing

单元测试

Test individual functions/methods
Mocking dependencies
Fast execution
Examples: Jest, Pytest, Mocha

测试独立函数/方法
模拟依赖项
执行速度快
示例：Jest、Pytest、Mocha

Integration Testing

集成测试

Test component interactions
With real databases/services
Slower than unit tests
Examples: Postman, Supertest

测试组件间交互
使用真实数据库/服务
比单元测试慢
示例：Postman、Supertest

End-to-End Testing

端到端（E2E）测试

Complete user workflows
Browser automation
Slowest but most realistic
Examples: Cypress, Selenium, Playwright

完整用户工作流
浏览器自动化
速度最慢但最贴近真实场景
示例：Cypress、Selenium、Playwright

Property-Based Testing

基于属性的测试

Generate random inputs
Verify invariants hold
Find edge cases
Examples: Hypothesis, QuickCheck

生成随机输入
验证不变量是否成立
发现边界情况
示例：Hypothesis、QuickCheck

Contract Testing

契约测试

Verify API contracts between services
Consumer and provider sides
Microservices testing
Examples: Pact, Spring Cloud Contract

验证服务间的API契约
包含消费者与提供者两端
微服务测试
示例：Pact、Spring Cloud Contract

Chaos Engineering

混沌工程

Inject failures intentionally
Test system resilience
Find weak points
Tools: Chaos Toolkit, Gremlin

主动注入故障
测试系统韧性
发现薄弱点
工具：Chaos Toolkit、Gremlin

Best Practices

最佳实践

Test Behavior, Not Implementation - Focus on what, not how
Keep Tests Fast - Run frequently
Isolate Dependencies - Mock external systems
Clear Test Names - Describe what's being tested
DRY Tests - Eliminate duplication
Test Edge Cases - Boundaries, nulls, errors
Use Test Fixtures - Consistent setup
Automate Testing - CI/CD integration

测试行为而非实现 - 关注「做什么」，而非「怎么做」
保持测试快速 - 频繁运行
隔离依赖项 - 模拟外部系统
清晰的测试命名 - 描述测试内容
测试代码遵循DRY原则 - 消除重复
测试边界情况 - 边界值、空值、错误场景
使用测试夹具（Test Fixtures） - 一致的前置设置
自动化测试 - 与CI/CD集成

Test Naming Convention

测试命名规范

test_[function]_[scenario]_[expected_outcome]

Example:
test_calculateDiscount_withValidCode_returnsDiscountedPrice
test_loginUser_withInvalidPassword_throwsAuthenticationError

test_[function]_[scenario]_[expected_outcome]

Example:
test_calculateDiscount_withValidCode_returnsDiscountedPrice
test_loginUser_withInvalidPassword_throwsAuthenticationError

Example Test Patterns

测试模式示例

AAA Pattern (Arrange-Act-Assert)

AAA模式（准备-执行-断言）

javascript

test('calculateTotal with items', () => {
  // Arrange
  const cart = new Cart();
  cart.addItem({ price: 10 }, 2);
  
  // Act
  const total = cart.getTotal();
  
  // Assert
  expect(total).toBe(20);
});

javascript

test('calculateTotal with items', () => {
  // 准备（Arrange）
  const cart = new Cart();
  cart.addItem({ price: 10 }, 2);
  
  // 执行（Act）
  const total = cart.getTotal();
  
  // 断言（Assert）
  expect(total).toBe(20);
});

BDD (Behavior-Driven Development)

BDD（行为驱动开发）

gherkin

Feature: User Authentication
  Scenario: Login with valid credentials
    Given a user with email "test@example.com"
    When the user logs in with correct password
    Then they should see the dashboard

gherkin

Feature: User Authentication
  Scenario: Login with valid credentials
    Given a user with email "test@example.com"
    When the user logs in with correct password
    Then they should see the dashboard

Metrics

指标

Code Coverage: % of code executed by tests (aim for 80%+)
Test Pass Rate: % of tests passing
Test Execution Time: How long tests take to run
Mutation Score: % of introduced bugs caught

代码覆盖率：测试执行覆盖的代码占比（目标80%+）
测试通过率：通过的测试占比
测试执行时间：测试运行所需时长
变异分数：捕获到的引入bug的占比

Common Pitfalls to Avoid

需避免的常见陷阱

Over-testing trivial code
Not testing error paths
Flaky tests (non-deterministic)
Testing implementation details
Ignoring performance in tests
Not testing concurrency

过度测试琐碎代码
未测试错误路径
不稳定测试（非确定性）
测试实现细节
在测试中忽略性能
未测试并发场景

References

参考资料

Test Driven Development (Kent Beck)
Growing Object-Oriented Software, Guided by Tests
Working Effectively with Legacy Code (Michael Feathers)
Testing Strategies for Microservices
Chaos Engineering (whitepaper)

《测试驱动开发》（Kent Beck）
《测试驱动的面向对象软件开发》
《修改代码的艺术》（Michael Feathers）
微服务测试策略
《混沌工程》（白皮书）