由于大量的电话型号，已经建立是不可能的测试也都不同类型。
Due to the huge number of Phone models that have been created it is impossible too test every different type.
今年早些时候，研究小组使用了一个40平方米的长方形尼龙帆，对克莱蒙斯的不可能理论进行了测试。
Earlier this year, the team put Clemmons's unlikely theory to the test, using a 40-square-metre rectangular nylon sail.
当一个合并不可能或者还没有被实现时，数据池中的行将会被排斥，并且测试活动是未定义的。
When a combination is not possible or not yet implemented, the row in the data pool is excluded and the test action is undefined.
由于依赖关系的原因，不可能对所有测试类型都采用操作系统虚拟化。
Adopting operating system virtualization for all test types is not possible because of dependencies.
由于测试没有覆盖到，这样的话就不可能修复大多数严重的可用性问题。
If you do, it will be impossible to fix the vast majority of the critical usability problems that the test uncovers.
在现实世界里，你不可能制作五个版本的新奥尔良城市并分别对其发动五个飓风袭击来测试各种后勤能力。
In the real world, you can't create five versions of New Orleans and throw five hurricanes at them to test different logistics.
此外，其他应用程序可能在更改后端资源上的数据，这将增加重复测试的困难，甚至不可能进行。
Additionally, the other applications may be changing data on the backend resources, making repetitive tests difficult or impossible.
不可能从图1中的得知的是，回归套件中的所有测试是否在某一处都运行了。
It is impossible to ascertain from this chart in Figure 1 whether all of the tests in the regression suite have been run at some point.
没有一次回归达到100%完成——不可能说出余下的测试对整个质量陈述是否重要。
None of the regression runs has achieved 100% complete — it is impossible to tell whether the remaining tests would be significant to the overall quality statement or not.
测试一个“有时候”运行的特性是不可能的。
It's impossible to test a feature that operates "sometimes."
在测试或登录时，可能会出现几种错误(但是如果按照本文档操作，这是不可能的)。
Upon Testing or logging in, several errors may occur (though if you followed this document, this is improbable).
因为我不可能去测试每个路由器，所以我只能在这方面给你一个通用的方向。
As I don't have every router available to test with, I can only give you general directions in this area.
如果没有测试框架，编写一套可维护的自动化单元测试几乎是不可能的。
Writing a suite of maintainable, automated unit tests without a testing framework is virtually impossible.
使测试都变得相同很明显是复杂的，也可能事实上是不可能的。比如说一只生活在水中的海豚和一匹生活在陆地上的马。
Making the tests equivalent, however, for say a dolphin that lives in the water and a horse that lives on the land is obviously complicated and may prove to be virtually impossible.
对于开发测试和系统测试环境有可能是这样，但是由于其他运行时环境的限制，使得这些操作即使不是不可能的，就是不切实际的。
This may be possible for development test and system test environments, but other run time environments have restrictions that make such practices impractical, if not impossible.
如果主题设计人员不可能精确地预测内容结构的变化，至少应尝试通过预期和测试预测出80%的情况。
If a theme designer cannot predict exactly how the content structure changes, then they can try to predict at least 80% of the scenarios through anticipation and testing.
对于开发测试和系统测试环境来说这是可能的，但是其它的运行时环境存在约束，所以这种方式是不可能的。
This may be possible for development test and system test environments, but other run time environments have restrictions that make such practices impossible.
一套适当的自动化功能测试也不可能捕捉到每个错误，但是它能比最好的单一单元测试捕捉更多的错误。
A maintained, automated suite of functional tests might not catch everything either, but it will catch more than the best suite of unit tests can catch alone.
构建CMIS客户端或工具时要记住一点：如果只使用一个存储库进行测试，要构建一个与 CMIS 真正兼容的客户端几乎是不可能的。
When you build a CMIS client or tool, remember it is virtually impossible to build a truly compatible CMIS client if you only test with one repository.
至于YAGNI，我认为如果没有测试推动您实现那种简单性，它不可能使您的设计简单。
As for YAGNI, I don't think it's possible to keep your design simple without having tests drive you to that simplicity.
理论上，测试一个版本的构建、然后错误地部署另一个版本，这样的事情不可能发生。
In theory there is no possibility of testing a build and then deploying a different build by mistake.
很难或者基本不可能在不同的测试脚本中重用测试脚本基线，或者基线组。
It's hard or impossible to reuse test script lines or groups of lines in different test scripts.
同样，没有测试告诉我是否破坏了某些内容，我就会发现集体所有权非常荒唐，持续的集成也是不可能的。
Likewise, without tests to tell me if I broke something, I would find collective ownership insane and continuous integration impossible.
全系统的压力测试可能着重突出一般性披露和不可能在一个公司测试时看见的拥挤买卖策略。
Systemwide stress tests might also highlight common exposures and "crowded trades" that would not be visible in tests confined to one firm.
当测试一个抵御模糊攻击的应用程序时，不可能做纯黑盒测试，但通过一些明显的修改，基本的想法还是可以应用的。
When you're testing a fuzz-resistant application, you can't do pure blackbox testing, but with some obvious modifications, the basic ideas still apply.
随着代码库的增长，手动测试已经变成不可能完成的任务，无论是大是小，所有代码的变化都会对整个应用程序产生影响。
As the code base grows, manual testing becomes an impossible task, and every code change made, big or small, could affect the entire application.
就像单元测试一样，如果没有测试框架，编写一套可维护的自动化功能测试实际上是不可能的。
Like unit tests, writing a suite of maintainable, automated functional tests without a testing framework is virtually impossible.
然而很遗憾，测试不可能涵盖所有用户的配置类型，所以碰到这种问题的最好解决方法是提交一个bug报告，（如果 bug 修正一切顺利）这个问题就不复存在了。
Unfortunately though, it is impossible to try it with everyone's configuration, so the best thing to do in a case like this is to submit a bug report so that (all going well) it will not happen again.
监控开关都是按照所有相关管理机关的要求在工厂进行预置和测试。一旦阀门装配后，就不可能进行调整。
Supervisory switch is preset and tested in accordance with all applicable agency requirements at the factory. No adjustment is possible once the valve is assembled.
PMD不可能找到每个bug，您仍然需要做单元测试和接受测试，在查找已知bug时，即使是PMD也无法替代一个好的调试器。
It won't find every bug — you still need to do unit testing and acceptance testing — nor is PMD a substitute for a good debugger when you're hunting down a known bug.
应用推荐