Further, test-last tools cannot support Acceptance Test Driven Development (ATDD).
进一步说，“最后再测试”工具无法支持“验收测试驱动开发（Acceptance Test Driven Development）”。
There has been a lot of activity in the Functional Test Driven Development world of late.
近来在功能测试驱动开发领域有很多活动。
This resembles test Driven Development (TDD), where Unit tests are supposed to be written before the code.
这有点像测试驱动开发(Test Driven Development,TDD)，单元测试应在代码之前编写。
Several of the practices outlined here can be categorised as general Test Driven Development (TDD) practices.
本文概述的实践中，有一些可归类到常用的测试驱动开发(TDD)实践。
Probably the most surprising revelation is the increased emphasis on test driven development and dependency injection.
或许最令人惊讶的事实是日渐增长的对于测试驱动开发和依赖注入的重视。
Test Driven development overcomes many of the issues faced by development teams that often leave the creation of Unit Tests until after the implementation.
测试驱动开发能克服开发团队遇到的许多问题：开发团队经常在代码实现之后才创建单元测试。
At first it’s faster to write code without tidying up, without writing unit tests, without doing Test Driven Development, so the team churns out more stories.
项目编码初期，不整理代码，不写单元测试，也不做测试驱动开发，整个团队粗制滥造出更多的“故事场景”。
Test driven development, in the context of reusable frameworks, is seen as a way to design frameworks that are actually usable rather than simply speculative.
在可重用框架的场景下，通过测试驱动开发设计出的框架是真实可用的，而不是简单地推理。
The practice of test driven development - and continuous integration, if implemented properly, reduces the chance of low quality products being released for QA testing.
测试驱动开发的实践——加上持续集成，如果实施得当，就能大大减少低质量产品流入测试阶段的机会。
If you follow the practice of test-driven development, you will actually develop your tests before you develop your code.
如果你遵循测试驱动开发的实践，那么实际上你将在开发你的代码之前开发你的测试。
It talks not only about the mechanics of how to write tests and allow them to drive your code, but also why test-driven programming is such a good thing.
该书不仅讲述了如何编写测试和让这些测试来驱动您的代码的原理，而且还讲述了测试驱动的编程为什么是一种好的编程方法。
This is consistent with test-driven development practices.
这与测试驱动的开发实践是一致的。
In the previous two installments of this series, I discussed how using test-driven development (TDD) helps you incrementally discover design.
在这个系列的前两期中，我讨论了如何使用测试驱动开发(TDD)帮助您逐步发现设计。
Some of them adapt well to using a test-driven development style.
有些人非常好的适应了测试驱动的开发方式。
In test-driven development automated tests should be written in the first place, in comparison to manual tests performed by team members.
在测试驱动开发中，跟团队成员执行的手动测试相比，自动测试的编写应该放在首要位置。
For example, you may start with iterative and test-driven development, and then follow up with pair programming and collocated teams.
比如，您可以以迭代和测试驱动开发开始，然后可以遵循成对编程和配置团队的原则。
I don't remember which one of suggested we ask questions for each chapter, effectively making it also test-driven.
我不记得我们中是谁建议在编写每章之前提出问题，这就采取了测试驱动的方式，而且很有效。
GUI testing is much more time-consuming and difficult than unit testing and thus often neglected, even in generally test-driven development teams.
与单元测试相比，GUI测试要耗时和困难的多，即使是在测试驱动的开发团队中，因此也常被忽视。
Refactoring is an essential step in test-driven development, providing the necessary feedback that allows your design (and code) to improve as the product develops.
倘若必要的反馈要求你的设计(和代码)在产品开发中得到改进，则重构是测试驱动开发中不可缺少的步骤。
Two recent, big changes in software engineering have been the growing use of test-driven development and continuous integration.
在软件工程方面，两个最近的重大变化是对测试驱动的开发和持续集成的使用日益增加。
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.
我们用的是测试驱动的方法，首先写一个我们希望通过的测试，一旦这个测试通过，我们再回头看我们可以怎么来优化代码。
Extended traditional test-driven development methodologies to ensure the system regression suites evolved with all new features and fixes.
扩展传统测试驱动开发方法系统，确保系统回归测试套件随所有新特性和补丁演变。
Continuous integration is often intricately linked with the practice of test-driven development.
持续集成常常与测试驱动的开发实践杂乱的链接在一起。
Next up: I talk about emergent design through test-driven development, which I've renamed test-driven design.
下一部分：我将通过测试驱动开发（我已经将其命名为 测试驱动设计）讨论紧急设计。
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.
在我用那种方式向大多数程序员说明这种情况时，他们认为测试驱动的编程是一个不错的想法 ― 这之后，他们仍然不使用这种方法。
Nevertheless, test-driven portal application development requires broadening the unit test approach.
然而，测试驱动的门户应用程序开发需要拓展单元测试方法。
In many projects, developers write unit tests at the same time — or sometimes even before (as in test-driven development) — they write their code.
在许多项目中，开发人员在书写代码的同时书写单元测试——或者有时甚至提前(如在测试驱动开发中)。
I created some unit tests for my task library to ensure tasks were being created properly and begun some test-driven refactoring.
我为我的任务库创建了一些单元测试，以保证任务可以被正确地创建出来，并且以测试驱动重构迈开第一步。
A general principle of test-driven development is that you should test all published interfaces to a class.
测试驱动的开发的总体原则之一就是应测试一个类已发布的所有接口。
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应用程序编写单元测试。
应用推荐