29%的“隐形风险”人群在三项测试中得分较高：他们每天花在电子设备上的时间超过5个小时。
29%, the "invisible risk" group, scored high on three in particular: They spent five hours a day or more on electronic devices.
通常会有几个回合，一次测试可以持续2到3个小时！
There are normally several rounds, and a quiz can go on for 2 to 3 hours!
这要求执行72小时或更长时间的负载测试。
This requires execution of load tests of 72 hours or longer.
所以，将这个用例的测试目标设置为每小时 12738 个事务。
The test target of this case was set at 12738 transactions per hour.
我们运行了这个测试几个小时以确保它是可重复的和可预见的。
We ran this test for several hours to make sure it was repeatable and predictable.
总测试时间为23小时，包括创建数据库。
The overall test time was 23 hours, including database creation.
测试的时间长度是每个测试各运行一个小时。
为了衡量每个场景中的性能影响，在MOM策略启动和关闭时都进行一小时的测试。
To measure the performance impact within each scenario, one-hour tests were completed both with and without the MOM policy active.
英国石油公司说，压力测试耗时六至48小时。
The pressure tests could take between six and 48 hours, BP said.
在很多场合下，只需几个小时即可创建并测试一个定制TD i装配线。
In many cases, a custom TDI assembly line can be created and tested in just a few hours.
英国石油公司星期四晚间完全关闭了井盖上的阀门，这是检查顶盖是否能够彻底抑制油井漏油的48小时测试的一部分。
BP completely shut the valves on the cap late Thursday as part of a 48-hour test to see if the cap can fully contain the oil leaking from the well.
同时，它将测试一个72小时持续任务运行训练和任务管理功能。
At the same time, it will test a 72-hour continuous mission operations exercise and mission management functions.
在几个小时的行走测试之后我的植入一步步深入了。
My empathy has clearly deepened after a few hours of road-testing it.
当我们在同一天中12小时过后测试受试者，发现他们准确率达到70%。
When we tested subjects 12 hours later on the same day, however, they made the correct choice 70 percent of the time.
DBA通常测试早上的两个小时工作负载，然后测试下午的两个小时工作负载，最后测试晚上的批处理查询。
The DBAs generally test the morning workload for two hours, then the afternoon workload for two hours, and finally the batched queries at night.
等一段时间，让DNS修改能够传播开(我们感觉需要2到4小时)，然后开始测试。
After some delay to allow the DNS changes to propagate (2 to 4 hours is what we experienced), you can start testing things.
这个吞吐量降低问题发生在一次为期3小时的压力比较测试中。
This throughput degradation problem occurred in a 3-hour stress comparison test.
主要的问题是在测试间隔（例如，3小时）期间，吞吐量逐渐降低，并且WebSphere应用程序的响应时间变得越来越长。
The main problem is during the test interval (for example, 3 hours), the throughput is decreasing gradually and the response time of WebSphere application is getting longer and longer.
测试时间约6个小时。
即便是是克隆了五个大型生产节点，并且用了一个小时来测试新部署，可能也只是花上个几美元而已。
And on top of that you only pay for what you use so even if you clone a large 5 node production cluster and use it for 1 hour to test a new deployment, it will probably only cost you a few dollars.
还有1600小时的飞行测试要做。
还有1600小时的飞行测试要做。
我第一次用Jersey和NetBeans时，不到半个小时就测试并运行起来了，包括下载、安装及代码浏览等。
I used Jersey and NetBeans for the first time, and was up and running within a half an hour, and that included downloads, installations and code surfing.
测试的时间长度是这6个测试各运行一个小时。
The test duration was one hour for each of these six test runs.
不仅如此，您还修改了 CruiseControl，从而只在（代码）签入时运行真正的单元测试，并以小时为基础运行组件测试。
Moreover, you modify CruiseControl to only run your true unit tests on check-ins and component tests on an hourly basis.
然而，如果一个完全的单元测试集要花一个小时运行呢？
However, what if a complete unit-test suite takes an hour to run?
不进行测试则会让您经受数小时的调试煎熬。
不进行测试则会让您经受数小时的调试煎熬。
应用推荐