When I write tests first, I have fantastic logic coverage.
在我先编写测试时，我有许多奇异的逻辑。
With a little practice, any programmer can write tests first.
采用这一点做法，任何程序员都可以先编写测试。
It's true, when you write tests first, you cannot write a whole algorithm.
是的，当你首先编写测试时，你不能编写一个完整的算法。
Many programmers who don't write tests first don't even know it's an option.
许多没有先编写测试的程序员甚至不知道还可以使用这种方法。
Even if they know how and think it's a good idea, many people still don't write tests first.
即使他们知道如何去做，并认为它是一种好的想法，但许多人仍然没有先编写测试。
As you write tests first and get them to pass, you're letting the code tell you what it wants to do and become.
在您先编写测试并通过测试这个过程中，您正在让代码告诉您它想要做什么，以及会成为什么。
These folks are smart, they have lots of experience, and they say they don't need to write tests first because they know what they're doing.
这些程序员很聪明，他们具有许多经验，他们说不需要先编写测试，因为他们知道自己在做什么。
Write the tests first. No, really.
测试先行不要惊讶，我是说真的。
First, I'll turn off the part of my brain that wants to do TDD and just write the solution, then write the tests for it.
首先，我将打消想要执行tdd的念头并且只是编写解决方案，然后为它编写测试。
When tests are written often (note, I'm not implying first), developers have the tendency to write uncomplicated code because complicated code is hard to test.
在编写测试时(注意，我没有暗示是第一次)，开发人员通常倾向于编写不太复杂的代码，因为复杂的代码难以测试。
One of the practices of test-driven development (TDD) is to write the tests first, then "do the simplest thing that could possibly work" -- in this case, return 6.
测试驱动的开发 (TDD)中的一个练习就是首先编写测试，然后执行可能运行的最简单的操作 —— 如本例中的 return 6。
The first article in this series introduced zope.testing, py.test, and nose, and began to describe how they can change the way that Python projects write and maintain their tests.
本系列中的第一篇文章介绍了zope . testing、py . test和nose，介绍它们如何影响Python项目编写和维护测试的方式。
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.
项目编码初期，不整理代码，不写单元测试，也不做测试驱动开发，整个团队粗制滥造出更多的“故事场景”。
XP demands that you write tests before you write code, so a simple design is one that grows over time in a test-first manner.
XP要求您在写代码之前先写测试，所以简单设计是以一种测试当先(test - first)的方式逐渐增长的。
As you saw in the first article, both py.test and nose have made tests in Python vastly easier to write by supporting tests that are written as simple functions, like.
正如在第一篇文章中看到的，py . test和nose都支持编写为简单函数的测试，这会大大简化python测试的编写。
Before you can start to write unit tests that evaluate database objects, you must first create a test project.
首先必须创建一个测试项目，然后才能开始编写用来评估数据库对象的单元测试。
Write the tests first and do not think about the implementation, just write them down like you think the final code should look or like you want to have your game code.
一开始写单元测试，不用考虑执行，只用把他们按你想象的最终代码那样写下来。
When the test passes, you got it. When adding a feature, first write tests that require it. This helps you understand what the feature ought to do, and to know when you got it right.
运行测试套件（至少也是其中的相当的一部分）应该成为你开发周期的一部分。
When the test passes, you got it. When adding a feature, first write tests that require it. This helps you understand what the feature ought to do, and to know when you got it right.
运行测试套件（至少也是其中的相当的一部分）应该成为你开发周期的一部分。
应用推荐