Skip to content

Commit

Permalink
Site updated: 2024-09-09 15:56:51
Browse files Browse the repository at this point in the history
  • Loading branch information
Jiajun-Peng committed Sep 9, 2024
1 parent 3c7cec7 commit 39c25e5
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 404 deletions.
2 changes: 2 additions & 0 deletions blogs/45253/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -302,6 +302,8 @@ <h1 id="第二章-什么是单元测试"><a href="#第二章-什么是单元测
<li>The two schools of unit testing: classical and London 单元测试的两个流派:经典和伦敦 </li>
<li>The differences between unit, integration, and end-to-end tests 单元、集成和端到端测试之间的区别</li>
</ul>
<span id="more"></span>

<p>As mentioned in chapter 1, there are a surprising number of nuances in the definition of a unit test. Those nuances are more important than you might think—so much so that the differences in interpreting them have led to two distinct views on how to approach unit testing.</p>
<p>正如第一章所提到的,在单元测试的定义中,有许多令人惊讶的细微差别。这些细微差别比你想象的要重要得多–以至于对它们的解释的差异导致了对如何进行单元测试的两种不同观点。</p>
<p>These views are known as the classical and the London schools of unit testing. The classical school is called “classical” because it’s how everyone originally approached unit testing and test-driven development. The London school takes root in the programming community in London. The discussion in this chapter about the differences between the classical and London styles lays the foundation for chapter 5, where I cover the topic of mocks and test fragility in detail.</p>
Expand Down
Loading

0 comments on commit 39c25e5

Please sign in to comment.