If you created an action recording when you ran Test a, you cannot replay it when you run Test B.
如果运行测试a时创建了操作录制，则无法在运行测试b时播放该录制。
We believe that if animals ran the labs, they would test us to determine the limits of our patience, our faithfulness, our memory for terrain.
我们相信，如果让动物在实验室里工作，它们会测试我们，以确定我们的耐心、忠诚和对地形记忆的极限。
I didn't finish the test— I ran out of time.
我没答完试卷，我的时间不够了。
Slow, crowded and often uncomfortable trains ran across this vast country, with low average speeds making journeys such as Shanghai-Beijing a test of travel.
缓慢、拥挤且经常不太舒服的火车曾横跨这个幅员辽阔的国家，其较低的平均速度使得从上海到北京这样的旅程都是一种考验。
Ran the application on the test server.
在测试服务器上运行应用程序。
However, this was the first test that actually ran the compiled test program instead of stopping once the program was compiled successfully.
无论如何，这是第一个这样的测试，它真正运行编译过的测试程序，而不是程序编译成功后就停止。
Since it's a new test, we ran it at least twice on each phone and took the average.
因为这是个新的测试，所以我们在每支手机上至少进行两次，取平均值。
We ran this test for several hours to make sure it was repeatable and predictable.
我们运行了这个测试几个小时以确保它是可重复的和可预见的。
You ran your unit test -- many times, perhaps -- and it worked perfectly every time.
您运行单元测试 --也许很多次 --并且它每次都运行得很好。
So easy, in fact, that when I first ran it on a test LPAR, I managed to lock myself out completely!
它是如此简便，实际上当我在一个测试LPAR上初次运行它时，我把自己完全挡在外边了！
But they ran a different kind of test and they got this.
但他们做了一个不同的检验，结果是这样。
After some promising initial trials, however, the test team simply ran out of time on their laser lease.
然而，在充满希望的几次初试后，测试队伍的激光器租期却到了。
The stop-ship test scenarios were generally those test cases which ran in a previous iteration and were carried forward as regression scenarios.
停船测试场景一般是那些在前面的迭代执行，并作为归回场景转到当前迭代的测试案例。
I ran the test and implemented code to make the test pass.
运行这个测试案例并实现代码使测试通过。
If everything ran and the test passed, the bar would be green.
如果可以运行，并通过测试，则会显示一个绿条。
Listing 11 shows the test I ran to prove it.
清单11展示了我为证明上述问题而运行的测试。
I ran the performance test separately on every JAX-RS implementation framework.
我分别在每个JAX - RS实现框架上运行这个性能测试。
At the very least, we ran scripts to test all areas of the system that might have been affected by defects we'd addressed.
至少我们运行了脚本来测试被我们已经解决了的缺陷所影响的系统部分。
We then ran the application on a test server and observed the output.
我们随后在测试服务器上运行了该应用程序，并对其输出进行了观察。
We ran a functional test and a performance and scalability test of the finished work.
我们运行了一个功能性测试，并在已完成的项目上运行了一个性能和可扩展性测试。
The output to the cactus_client.log file, typically written to the root of the Application Developer installation, should resemble the following if the test case ran successfully.
如果测试案例成功运行，那么输出到cactus_client . log文件的结果(通常写到Application Developer的安装根目录)应该类似于下面所示。
The test queries ran for a single user more than 100 times slower against the big cube [AllSales] that contains all the data than against the virtual cube [VirtualSales].
在每个用户的查询测试中，针对包含所有数据的大数据集 [AllSales] 的查询速度要比针对虚拟数据集 [VirtualSales] 的查询速度慢 100倍。
I also ran a test of Ruby's REXML, using the following script.
我也对Ruby的REXML进行了测试，使用了以下脚本。
That said it only ran once for each test case.
它只表示在每一次测试用例中只运行一次GC。
Also, I ran an informal performance test on all of the JAX-RS frameworks discussed using a sample RESTful service and an open source performance testing tool.
另外，我使用了一个样例RESTful服务和一个开源性能测试工具在所有这些JAX - RS框架上运行了一个非正式性能测试。
To test the final implementation, you created and ran a client using Axis2.
然后使用Axis2创建和运行客户机，来测试最终的实现。
Instead of using anything fancy, I simply ran a test on the status attribute, as in Listing 12.
为了简便起见，我只对status属性运行了一个测试，如清单12所示。
In the second test, we ran the 4000 NotesBench DWA85 simulated users, going through the BIG-IP LTM proxy, and accessed their mail servers.
在第二个测试中，有4000个NotesBenchDWA85模拟用户，经过BIG - IP LTM代理，然后访问邮件服务器。
Note: These statistics were generated from 2-second-interval vmstat logs that we ran during the test procedure.
注意：这些统计数字是由我们在测试过程中运行的2秒钟间隔的vmstat日志生成的。
Note: These statistics were generated from 2-second-interval vmstat logs that we ran during the test procedure.
注意：这些统计数字是由我们在测试过程中运行的2秒钟间隔的vmstat日志生成的。
应用推荐