The wire in question passed all normal production tests.
测试电线通过所有常规测试。
Production tests indicate it is easy to master this technology.
通过生产试验，基本上掌握了生产技术要求。
Lifetime testing is one of the most common types of production tests that cell phone handsets undergo.
寿命测试是手机需要经过的最常见的一种生产测试。
The steel and the heat treatment process of fine heavy load drift was determined by means of production tests. And the satisfactory result was obtained.
经应用试验，确定了精密重载冲孔模的用材及热处理工艺，获得满意的效果。
The Ningwu Basin is proved to be abundant in CBM by evaluation for exploration of coalbed methane, optimization of prospects and early production tests in the Ningwu Basin, Shanxi Province.
通过在山西宁武盆地开展煤层气勘探评价工作，对目标区优选及前期抽排试验，证实了宁武盆地具有一定的煤层气资源。
By repeating technological tests and batch production tests for over a year, the fused silica was successfully used in the production of silica sol shell for low temperature wax precision casting.
经过反复的工艺试验及一年多批量生产验证，成功地将熔融石英应用于精铸用低温蜡—硅溶胶型壳生产中。
What I would advise you would be to load it (the library itself, and the scripts with your tests) automatically in a development and test environments, removing them when in production.
我建议你在开发环境和测试环境中自动加载(测试库本身和测试脚本)，在生产环境中则要删除。
Note that Design by Contract tests can be turned off in production deployments to remove their overhead.
注意，在生产部署时可以关闭契约式设计测试，以消除它们的开销。
This means that you can use it in any number of different circumstances: unit tests, production code, and so on.
这意味着您可以在不同的情况下使用它：单元测试、生产代码，等等。
For the most accurate results, the investigation tests should be run against full production data.
要想获得最准确的结果，就应该针对完整的生产数据进行测试。
If the application fails the tests, you can send it back to development before it is moved into production — where a failure can have huge consequences.
如果应用程序经过测试是失败的，你可以将它在产品成型之前返回到开发部门——这样就避免了后期巨大的损失。
The tests are automatically run in a separate environment that interferes with neither your development environment nor your production environment.
测试在不妨碍开发环境和生产环境的情况下自动地在分离的环境中运行。
Indeed tests are even more important for legacy systems already in production.
对于已经在生产中的遗留系统，测试确实更加重要。
I'm not suggesting that running true integration tests against your production database is a waste of time.
我并不是暗示运行对生产数据库运行实际的集成测试时浪费时间。
An integration developer makes technical updates to the model, unit tests, then exports the model to an EAR file for deployment to the test and production servers.
集成开发人员对模型进行技术更新、单元测试，然后将模型导出到EAR文件，以便部署到测试和生产服务器。
We never actually got the code to pass its tests on a more realistic operating system and the production middleware.
实际上，代码并没有通过更趋于实际的操作系统和生产中间件的测试。
One of the best security tests to perform before an SOA is moved to production is a penetration test.
要在将SOA转移到生产环境之前执行的最合适安全测试之一是渗透测试。
It is intended for functional tests, not for production.
它主要用于功能测试，不用于生产。
With automated migration, teams can regularly perform dry runs that deploy the code into a clean "production class" environment, where automated unit and system-level tests may be executed.
在自动化移植中，团队可以将代码转入干净的“生产级”环境，在那里可以执行自动化的单元和系统级测试。
For example, if the production machine has 6 400hm CPUs, the test machine should also have 6 400hm CPUs; otherwise your subsequent tests will be invalid and not reliable.
例如，如果生产机器有6个400hm的CPU，那么测试机器也应该有6个400hm的CPU；否则，随后的测试将是无效且不可靠的。
After the tests are run and the information is analyzed, the benchmark server can be converted back to a production server or can become a testing server with another focus.
运行测试并分析信息之后，瓶颈服务器可以转换为生产服务器，或者可以成为焦点不同的测试服务器。
An application must never be placed into the production environment until it has passed performance tests with the expected behavior.
应用程序在以预期的行为通过性能测试前绝不能被用于生产环境。
In the banking world the production world is heavily walled off, so it becomes tricky ensuring that a test database is meaningful and current and can be used concurrently with automated tests.
在银行业，产品世界更是和开发有着严格的分隔。所以在保证数据库测试普遍有用性的同时又能与自动测试并发，是需要很多技巧的。
Before writing any production code, we'd write our unit tests.
在实际开始编写产品代码之前，我们需要编写单元测试。
Very often, tests are less complex than the eventual production environment, so a program can contain a memory corruption error that will wreak havoc after release even though the tests all pass.
十分普遍地情况是，测试环境并没有最终的产品环境复杂，因此即使测试都通过了，程序也能够包含一个在发布版本后即将引起严重破坏的内存崩溃性的错误。
This meant that the test team had to devise tests to simulate production loads without the benefit of a user interface to prepare and submit middleware requests.
这意味着测试团队不得不在没有用户接口可以准备和提交中间件请求的情况下模拟生产负载。
Luckily, I learned that pushing untested code into production didn't work; consequently, I began to write unit tests.
幸运的是，我已经学到 绝不应该将未经测试的代码投入生产；因此开始坚持编写单元测试。
Luckily, I learned that pushing untested code into production didn't work; consequently, I began to write unit tests.
幸运的是，我已经学到 绝不应该将未经测试的代码投入生产；因此开始坚持编写单元测试。
应用推荐