Test-driven development and rspec.
测试驱动的开发和rspec。
Solidify requirements with test-driven development
通过测试驱动的开发来巩固需求
This is consistent with test-driven development practices.
这与测试驱动的开发实践是一致的。
Some of them adapt well to using a test-driven development style.
有些人非常好的适应了测试驱动的开发方式。
This feature greatly improves Visual Studio support for test-driven development (TDD).
此功能大大提高了测试驱动的开发(TDD)的VisualStudio支持。
Test-driven development allows you to defer decisions until you understand the problem better.
测试驱动开发允许你推迟决定，直到你更好地理解了问题之所在。
Continuous integration is often intricately linked with the practice of test-driven development.
持续集成常常与测试驱动的开发实践杂乱的链接在一起。
He came out of it realizing that there is a whole style to test-driven development that he didn't expect.
最终他认识到，测试驱动开发完全不是他所期待的那样。
Next up: I talk about emergent design through test-driven development, which I've renamed test-driven design.
下一部分：我将通过测试驱动开发（我已经将其命名为 测试驱动设计）讨论紧急设计。
A general principle of test-driven development is that you should test all published interfaces to a class.
测试驱动的开发的总体原则之一就是应测试一个类已发布的所有接口。
The key to starting with test-driven development is to start at the top, and make as few assumptions as possible.
测试驱动开发入门的关键就是从零入手，尽量少地使用假设条件。
Test-driven development (TDD) alters the process of writing code so that change is not only possible, but desirable.
测试驱动开发（TDD）改变了编码的过程，并且这种改变不仅是可能的，同时也是值得去做的。
We chatted about Test-Driven Development (TDD) as a development practice, but what about overall project scheduling?
我们曾经聊过用测试驱动开发方式(test-driven development)来作为开发模式，但是整个项目的计划该怎么办？
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.
不过，现在还很难下结论，因为尝试过测试驱动开发的人还是少数。
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所示。
Test-driven development is an Agile development technique in which developers code test cases before implementing the service.
测试驱动的开发是一种Agile开发技术，其中开发人员在实现服务之前先编码测试用例。
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应用程序编写单元测试。
For example, you may start with iterative and test-driven development, and then follow up with pair programming and collocated teams.
比如，您可以以迭代和测试驱动开发开始，然后可以遵循成对编程和配置团队的原则。
The class consists of a large number of cohesive methods, which is a side-effect of using test-driven development in its construction.
类中包含大量的方法，这是采用测试驱动开发进行构建的副作用。
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)之类的概念，大多数人认为相当极端。
In test-driven development automated tests should be written in the first place, in comparison to manual tests performed by team members.
在测试驱动开发中，跟团队成员执行的手动测试相比，自动测试的编写应该放在首要位置。
Extended traditional test-driven development methodologies to ensure the system regression suites evolved with all new features and fixes.
扩展传统测试驱动开发方法系统，确保系统回归测试套件随所有新特性和补丁演变。
In the previous two installments of this series, I discussed how using test-driven development (TDD) helps you incrementally discover design.
在这个系列的前两期中，我讨论了如何使用测试驱动开发(TDD)帮助您逐步发现设计。
In many projects, developers write unit tests at the same time — or sometimes even before (as in test-driven development) — they write their code.
在许多项目中，开发人员在书写代码的同时书写单元测试——或者有时甚至提前(如在测试驱动开发中)。
Unit testing and test-driven development are excellent tools for managing such fragile systems with confidence, but they only work if you use them.
单元测试和测试驱动的开发这些出色的工具使您可以信心十足地管理此类脆弱系统 ——但只有在您确实使用了这些工具时，它们才能发挥作用。
GUI testing is much more time-consuming and difficult than unit testing and thus often neglected, even in generally test-driven development teams.
与单元测试相比，GUI测试要耗时和困难的多，即使是在测试驱动的开发团队中，因此也常被忽视。
If you've never encountered test-driven development (see Resources), you might object that no one would write such a simple-minded implementation.
如果您从未接触过由测试驱动的开发(请参阅参考资料)，那么您可能也会认为人人都能编写如此头脑简单的实现。
应用推荐