Writing test cases first lowers your risk in refactoring.
先编写测试用例会降低重构中的风险。
You'll talk more about writing test cases later in this book.
在本书的后面章节将会涉及更多的如何写测试案例。
Writing test cases early assists you by identifying and jump - starting the testing process.
通过识别和跳跃性地开始测试过程，书写测试用例可以向您提供很大的帮组。
Writing test cases against code naturally increases the collective confidence of a development team.
对一个开发团队而言，针对代码编写测试案例自然可以增加集体的信心。
In the next chapter, we will talk about writing test cases and the often frustrating task of debugging that follows.
下一章，我们要谈论编写测试用例，以及接下来的经常让人沮丧的调试任务。
In this chapter and the rest of the book, we emphasize the importance of writing test cases as an integral part of coding.
本书的剩下章节，我们强调的是编写测试案例作为代码完整性的一部分。
Much of the actual testing is performed by the SWEs, SETs are there to ensure that features are testable and that the SWEs are actively involved in writing test cases.
实际上大多数测试是由软件开发工程师执行的。测试开发工程师是确保特性的可测试项，而软件工程师则更多参与测试用例的编写。
You have to invest the time in writing the test cases and, of course, you need to run the test application regularly.
在编写测试案例方面，必须花费一些时间，当然，您需要经常运行这个测试应用程序。
Early involvement of the test team minimizes the dependency on supportive documentation for writing effective test cases.
测试团队及早介入，于是在编写有效的测试案例时，尽可能不依赖支持文档。
Ideally, the application developers themselves build the test cases for the code they are writing.
在理想状况下，应用程序开发人员自己为他们编写的代码构建测试用例。
Agile software development and extreme programming both promote writing unit test cases before developing the source code.
敏捷软件开发和极限编程二者均提倡在开发源代码之前编写单元测试用例。
The test cases are written first, and implementation proceeds by writing code to satisfy each test case.
将首先编写测试用例，然后将通过编写满足各个测试用例的代码来进行实现。
My high, however, isn't from writing the test cases; it's in seeing their results.
但是，我的兴奋不是来自编写测试用例，而是看着它们生效。
You could write some throwaway sample code, but if FixedList is going into production, you'd be better served by immediately writing some test cases for it.
您可以编写一些用后即扔的样例代码，但是如果FixedList 将投入到生产中，您最好立即为其编写一些测试用例。
If you use JUnit, the all-important question is, Do I have to stop writing JUnit test cases?
如果您使用的是JUnit，则最重要问题是：必须停止编写JUnit测试用例吗？
Having a bucket called "Testing" that doesn't include the time for writing the test cases.
有一个名为“Testing”的bucket，其中没有包括用于编写测试用例的时间。
Now let's apply this theory by writing a few simple test cases for the Quad example.
现在我们为Quad例子写一些测试用例来实践上述的原理。
Writing and implementing the test cases.
根据测试设计，编写并实施测试用例；
Writing and implementing the test cases.
根据测试设计，编写并实施测试用例；
应用推荐