Even if you don't succeed at this, you can still be proud of the tests and code you deliver.
如果没有成功地使之加入到流程中，您仍旧可以为您所撰写的测试和代码自豪。
The idea behind the name is that there are best practices for software development, such as writing unit tests and code reviews.
这个名称背后的思想是软件开发的最佳实践，例如编写单元测试和代码复查。
If you changed code or test Settings, you can run the latest versions of the tests and code under test while using the latest test Settings.
如果更改了代码或测试设置，可以使用最新的测试设置来运行测试和测试代码的最新版本。
As long as you keep your tests and code synchronized (and that's the whole point of the practice), if a programmer wants to know what the system does, he or she can look at the tests.
只要您保持测试和代码的同步(这是实践的关键点)，如果有程序员想知道系统能做什么，他或她可以参看测试。
Many developers use a variant of testing called test-after development (TAD), whereby you write the code and then write the unit tests.
许多开发人员使用称为后测试开发（TAD）的各种测试，你首先编写代码，然后编写单元测试。
Because it's all digital, it eliminates the used book market and eliminates any sharing, and because homework and tests are through an access code, it eliminates any ability to opt out.
因为它全是数字化的，它淘汰了二手书市场，也杜绝了任何共享，而且因为作业和考试都是通过准入码进行的，它让人们失去了选择退出的任何能力。
But because it's all digital, it eliminates the used book market and eliminates any sharing, and because homework and tests are through an access code, it eliminates any ability to opt out.
但因为它全是数字化的，它消除了二手书市场，也消除了任何共享，而且因为作业和考试都是通过准入码进行的，它消除了任何选择退出的能力。
Only after you have your tests written (and failing) do you write the code under test.
只有在编写了测试(并失败)后，您才可以编写测试中的代码。
If you want to try the tests on your own hardware and JVM, download the code.
如果您想要在自己的硬件和JVM上尝试这个测试，请下载该代码。
One way is to have a thorough set of unit tests for the code: the code should pass the tests both before and after refactoring.
第一种方法是对代码进行一套完全彻底的单元测试：在重构之前和之后都必须通过这样的测试。
And yet when I think about working to keep code well-factored and writing tests, I find that makes me go faster.
但当我回顾我自己的经历时，却发现保持代码的良好构造以及编写测试反而使我的工作加快了。
Similarly, changes that do have business value but would also have great impact on existing requirements, designs, code, and tests may not be worth the effort.
同样，有业务价值的变更也可能因为对现有的需求、设计、编码和测试影响过大而得不偿失。
And in my experience, my code is much simpler when tests drive it, and I'm always in the market for greater simplicity.
根据我的经验，在测试推动代码时，我的代码就会简单得多，而且我一直在设法使它们更为简单。
The activity also involves fixing code defects and performing unit tests to verify the changes.
此活动也包括修复代码缺陷和执行单元测试，以验证变更。
The developer responds by adding code and tests to the source control system.
开发人员作出反应，把代码和测试用例添加到版本控制系统中
You have to get used to the idea that you can and should write tests before you write code.
您必须习惯这种思想，在编写代码之前，可以并应该编写测试。
Upon completing the code and the unit tests, the developer creates a review package consisting of design specifications, code, unit test specifications, and unit test results.
在完成了代码和单元测试之上，开发人员创建一个由设计说明、代码、单元测试说明和单元测试结果组成的评审包。
Currently, the logic that assigns the tests and tests due date to a computer is part of this application's compiled code.
目前，为计算机分配测试和测试到期日期的逻辑是该应用程序的已编译代码的一部分。
All code must be tested, and ideally the tests should be written before the model code is.
所有代码都必须测试，而且理想情况下应该在编写代码之前编写测试。
Let's put it this way: I can be away from our code base for a month and with the unit tests and the well factored code, i can find whats going on in minutes.
让我们换个说法：我可以一个月不去看代码库，只要有单元测试和构造良好的代码，在几分钟之内我就能够了解现在的进展。
Programmatic proxy creation is useful when writing infrastructure code and tests, but is not often used in regular business applications.
编程式的代理创建在编写基础结构代码和测试时比较有用，但在通常的业务应用中并不经常使用。
This means that you can use it in any number of different circumstances: unit tests, production code, and so on.
这意味着您可以在不同的情况下使用它：单元测试、生产代码，等等。
A well-tested application doesn't consist merely of application code and tests.
一个测试良好的应用程序不仅仅包含应用程序代码和测试。
Compiles, tests, and packages your code.
编译、测试并打包代码。
With TDD the tests are thought out and created as the code is implemented.
使用测试驱动开发，在实现代码时，就要仔细考虑测试，并建立起测试。
Documentation rarely stays in sync with the code, so do only the minimum necessary and depend on clearly written code and tests for the rest.
文档很少与代码保持一致，因此只做那些最需要的事，余下的部分则取决于明确编写的代码和测试。
The practices rely on manual steps -- integrating code, running tests, and checking code in at the right times -- that can lead to mistakes.
目前的实践依赖手工步骤 ——集成代码、运行测试、在合适的时间检入代码，这样的实践有可能造成错误。
Typically the Business requirement is written and the team will drill down to flesh out the use cases that will drive the tests cases, the unit tests and ultimately the implementation code.
通常，编写完业务需求后，团队成员会进行深入的探讨，建立起具体的用例，由这些用例驱动测试用例、单元测试和最终代码的实现。
You are able to run and debug tests right from the code editor.
你能从代码编辑器中运行和调试测试。
You are able to run and debug tests right from the code editor.
你能从代码编辑器中运行和调试测试。
应用推荐