这会让测试用例失败。
Calls to unexpected methods cause the test to fail.
调用未预期的方法会导致测试失败。
Calls to unexpected methods do not cause the test to fail.
调用未预期的方法不会导致测试失败。
So move quickly, test often, fail fast, and discuss and document your assumptions.
所以快点行动，经常测试，快速失败，讨论并用文件记录你的假设。
There's a higher probability of detecting the fail if the test is run a couple times.
如果多次运行测试，就能够提高发现失败的可能性。
The DOH also allows you to specify a custom timeout in milliseconds that will fail the test if a response is not returned within the specified time.
DOH还允许以毫秒为单位设定超时值，一旦响应没有在指定的时间内返回，测试就会失败。
You may be asking yourself why this test will fail. After all, it is valid syntactically.
您可能会问这个测试为什么会失败，毕竟它的语法是正确的。
Chances are that the test will fail several times in the project life as the bug resurfaces.
在整个项目生存期中，当这个错误重新出现时，这个测试有可能会失败几次。
If during execution the total time exceeds this time, the test case will fail.
如果执行总时间超过了这个时间，测试样例将失败。
If the exception isn't thrown (or a different exception is thrown), the test will fail.
如果该异常没有抛出(或者抛出了一个不同的异常)，那么测试就将失败。
This test case will fail at assertion because the results page contains no link with this text.
这个测试用例遇到断言的地方会失败，因为结果页面中不包含带有这个文本的链接。
Therefore, the daily builds will continually fail as expected until the appropriate test cases are passing.
因此，每日的构建将如预料不断地失败，直到适当的测试用例通过。
Sometimes it's simplest to have a human sit in front of the program and mark each test as pass or fail.
有时，最简单的方法是让一个人坐在程序前将每一个测试通过或失败的结果都标记下来。
Repeat until you find a test that does fail and thus discover the true cause of the bug.
重复进行，直到找到一个真正失败的测试，从而找到造成bug的真正原因。
This is challenging because there is no network in a unit test and the AJAX call will fail.
这很有挑战性，因为单元测试中没有网络，AJAX调用会失败。
This is what indirectly causes the testDataLayer() test case (from Listing 3) to fail, by the way.
这将间接导致 testDataLayer()测试用例（如清单3所示）失败。
The default timeout value for asynchronous tests is 500 ms, or half a second, so many times it's a good idea to explicitly specify a longer timeout value so your test does not fail.
异步测试的默认超时值是500ms，也就是半秒，所以，很多时候，最好是显式地指定一个更长的超时值，这样一来，测试就不会失败。
These tests don't necessarily need to fail first (although a failure when you think a test should pass is pure gold, because you've found a potential bug).
这些测试不一定需要首先采用失败测试的形式（但是，如果在认为测试应该通过时测试却失败了，这是很有价值的，因为这意味着找到了一个潜在的 bug）。
Should you fail in the test, you could try again.
万一你考试失败了，你可以再试一次。
This is the most reliable way to find components in a test; it guarantees that component lookup will never fail, even if the GUI's layout changes in the future.
这是在一个测试中查找组件最可靠的方式；它保证组件查找从不失败，即使GUI的布局在将来会改变。
Scientists don't yet know why dogs fail this test, but it may be because "we train them to look at our eyes and face and not to follow our gaze," says Range.
科学家们现在还不知道为什么狗反而会在测试中失败，兰奇认为可能是因为“我们训练狗注视我们的眼睛以及面部，而不是追随视线。”
This code runs in a respectable time, but a couple of the test assertions fail.
这段代码运行的时间十分合理，但是几个测试断言都失败了。
So, write just enough code to get the test to compile, run, and fail.
因此，编写足够的代码来使测试进行编译、运行但结果失败。
Why is it that some software test teams succeed while others fail?
Illustration为什么有些软件测试团队成功了而另一些却失败了？
We started this discussion by asking, "Why is it that some software test teams succeed while others fail?"
我们从提出问题：“为什么有些软件测试团队成功而另一些却失败了？”开始进行讨论。
In JUnit 4, if your test suite consists of 1000 tests and 3 of them fail, you'll likely be forced to rerun the entire suite (with fixes).
在JUnit4中，如果测试套件包括1000项测试，其中3项失败，很可能就会迫使您重新运行整个测试套件(修改错误以后)。
If they are equal, the test will be considered successful; if they are not equal, the test will fail.
如果它们相等，则认为测试成功；如果它们不相等，则测试失败。
So the UI test automation will not catch the logic error if the application has the wrong method wired to a button click event (although every test would fail and you'd find the problem quickly).
所以如果应用程序为按钮单击事件关联了错误的方法，UI测试自动化不会捕捉到逻辑错误(虽然每次测试都会失败，而且您会很快发现问题)。
The test case in Listings 2 through 4 produce a NoClassDefFoundError because an implicit load of class B will fail
清单2到清单4的测试用例产生了NoClassDefFoundError，因为类B 的隐式装入会失败
Else code block is a simple logical crossroad that helps show why the test would fail or pass if one path - and not another - is taken, according to test expectations.
else代码块是一个简单的逻辑分支，根据测试期望说明选取一条路经——而不是另一条路经——之后测试将失败(或通过)的原因。
应用推荐