Solidify requirements with test-driven development
通过测试驱动的开发来巩固需求
When I do test-driven development, the hours fly by.
当我进行测试驱动开发时，时间过得飞快。
This is consistent with test-driven development practices.
这与测试驱动的开发实践是一致的。
Some of them adapt well to using a test-driven development style.
有些人非常好的适应了测试驱动的开发方式。
The good news is that test-driven development isn't just for new code.
好消息是，测试驱动开发不仅仅适合于新代码。
For test-driven development, you have to twist your thinking a little bit.
对于测试驱动开发，您必须稍微改变一下思考方式。
For many developers, the shift from test-driven development to BDD is a smart move.
对于很多开发人员来说，从测试驱动开发转移到BDD是明智的转变。
This feature greatly improves Visual Studio support for test-driven development (TDD).
此功能大大提高了测试驱动的开发(TDD)的VisualStudio支持。
Nevertheless, test-driven portal application development requires broadening the unit test approach.
然而，测试驱动的门户应用程序开发需要拓展单元测试方法。
It has extensive unit tests (in part because I wrote it for a discussion of test-driven development).
它具有丰富的单元测试(因为我编写的目的是用于探讨测试驱动开发)。
Jester would be extremely useful as an extra counter-check on code not written in a test-driven manner.
在对没有使用测试驱动方式编写的代码进行额外检查时，Jester尤为有用。
A general principle of test-driven development is that you should test all published interfaces to a class.
测试驱动的开发的总体原则之一就是应测试一个类已发布的所有接口。
I'm done with the test-driven version of the perfect-number finder; the entire class is shown in Listing 9.
最后，完成了完全数查找程序的测试驱动版本；完整的类见清单9。
If you follow the practice of test-driven development, you will actually develop your tests before you develop your code.
如果你遵循测试驱动开发的实践，那么实际上你将在开发你的代码之前开发你的测试。
Sorry, but test-driven development (TDD) is actually faster than just writing the code and throwing it over the wall to QA!
抱歉，比起只是写代码，然后抛给墙那边的QA去测试来说，测试驱动开发（TDD）确实更快！
However, I think it is hard to tell at the moment because not enough people have tried the test-driven development approach.
不过，现在还很难下结论，因为尝试过测试驱动开发的人还是少数。
Part 1 of this series on test-driven development in an SOA environment showed you how to write unit tests for SOA applications.
在这个有关SOA环境中的测试驱动的开发系列中，第1部分向您介绍了如何为SOA应用程序编写单元测试。
Two recent, big changes in software engineering have been the growing use of test-driven development and continuous integration.
在软件工程方面，两个最近的重大变化是对测试驱动的开发和持续集成的使用日益增加。
Using the same test-driven development techniques, I created an alternate version of the classifier, which appears in Listing 2.
采用相同的测试驱动开发技术，可以创建该分类器的可替换版本，如清单2所示。
I created some unit tests for my task library to ensure tasks were being created properly and begun some test-driven refactoring.
我为我的任务库创建了一些单元测试，以保证任务可以被正确地创建出来，并且以测试驱动重构迈开第一步。
When you do, they morph into concepts like test-driven development and pair programming, which most people view as rather extreme.
当您这样做时，它们就变成类似测试驱动的开发(Test - Driven Development)和结对编程(PairProgramming)之类的概念，大多数人认为相当极端。
We did it test-driven, starting with a test that we wanted to succeed and once it passed we looked into how we could improve the code.
我们用的是测试驱动的方法，首先写一个我们希望通过的测试，一旦这个测试通过，我们再回头看我们可以怎么来优化代码。
The class consists of a large number of cohesive methods, which is a side-effect of using test-driven development in its construction.
类中包含大量的方法，这是采用测试驱动开发进行构建的副作用。
When I explain it that way, most programmers I've talked to think test-driven programming is a good idea -- then they still don't do it.
在我用那种方式向大多数程序员说明这种情况时，他们认为测试驱动的编程是一个不错的想法 ― 这之后，他们仍然不使用这种方法。
In test-driven development automated tests should be written in the first place, in comparison to manual tests performed by team members.
在测试驱动开发中，跟团队成员执行的手动测试相比，自动测试的编写应该放在首要位置。
In the previous two installments of this series, I discussed how using test-driven development (TDD) helps you incrementally discover design.
在这个系列的前两期中，我讨论了如何使用测试驱动开发(TDD)帮助您逐步发现设计。
Developing a test framework in test-driven way isn't without its challenges, but once you have the basics working it goes surprisingly smoothly.
用测试驱动的方法来开发一个测试框架不是一点挑战都没有，但当你完成了基础工作后，它会非常之顺利。
In many projects, developers write unit tests at the same time — or sometimes even before (as in test-driven development) — they write their code.
在许多项目中，开发人员在书写代码的同时书写单元测试——或者有时甚至提前(如在测试驱动开发中)。
GUI testing is much more time-consuming and difficult than unit testing and thus often neglected, even in generally test-driven development teams.
与单元测试相比，GUI测试要耗时和困难的多，即使是在测试驱动的开发团队中，因此也常被忽视。
Unit testing and test-driven development are excellent tools for managing such fragile systems with confidence, but they only work if you use them.
单元测试和测试驱动的开发这些出色的工具使您可以信心十足地管理此类脆弱系统 ——但只有在您确实使用了这些工具时，它们才能发挥作用。
应用推荐