一些测试类型需要较少的CPU和磁盘空间，而另一些测试类型需要较高的 CPU使用率、I/O操作和磁盘使用率。
Some of the test types require less CPU and disk space, whereas some of the test types requires high CPU usage, I/O operations, and disk usage.
测试结束时，您将在控制台中看到一些或者两个这种类型(清单2)的异常。
At the end of the test, you see some or both of these types of exceptions in the console (Listing 2).
一旦将这些各式各样的开发人员测试类型合并到一个构建过程中时，可以将这些测试中的一些（或者全部）作为CI 过程的一部分运行。
Once you've incorporated the execution of these various developer test types into a build process, you can run some (or all) of these tests as part of a CI process.
在进行下一步前，让我们也看看一些会阻碍测试团队工作的人的类型吧，并探讨一下如何把他们的能量导入更有效的任务中。
Before we move on, let's also take a look at some types of folks who can actually impede work on a test team, and examine how to redirect their energies into more productive tasks.
如果你以前编写过动态类型语言，你会发现你的测试组其实会小一些，但不会小很多。
If you are coming from a dynamically typed language, you may find that your test suites are a little smaller, as a result, but not that much smaller.
我也定义了一些逻辑，将所有不同类型的测试结果合并到一个CruiseControl日志文件中。
I've also defined some logic to merge the results of all my different types of tests into a CruiseControl log file.
缺少IP混淆和对客户端数字证书的支持，限制了我使用RationalPerformance Tester为一些类型应用程序类型进行性能测试。
The absence of IP aliasing and support for client-side digital certificates have kept me from using Rational performance Tester for some of the types of applications I typically performance test.
我提供一个关于不同类型开发人员测试的概览，和一些可以添加到构建过程并使用ContinuousIntegration系统持续运行的例子。
I provide an overview of the different types of developer tests along with examples that you can add to your build process and run continually using a Continuous Integration system.
对我们的三个测试都进行了设置，现在我们能够看到一些不同的测试结果类型。
With our three test cases set up, we can now look at some different types of test results.
我们在早期做了一些负载测试，但是这个测试类型会在接近开发周期的尾声时达到最高点。
We'd done some load testing earlier, but this type of testing peaked near the end of the development cycle.
这些模型可以被一同使用，其中一些根据特性区域进行命名，另一些根据测试类型进行命名。
These models can be used together, with some plans named for feature areas and others named for test types.
所有形式都包含一些类型的必需权限集和一些类型的标识；这些测试中的形式将MockPrincipal对象用于标识。
All the forms involve some kind of required permissions set and some type of identity; the form in these tests USES a MockPrincipal object for identity.
除了使用更多的服务器以外，我们还使用了一些不同的Web客户机测试工具，包括WPT、Hammerhead、Httperf和Pagepoker，来模拟不同类型的用户环境。
In addition using more servers, we used several different Web client test tools, including WPT, Hammerhead, Httperf, and Pagepoker to simulate different types of user environments.
周围的人有一个测试应该知道，有一些限制，这种类型的测试。
People having a peripheral test should be aware that there are some limitations with this type of test.
介绍了H263 +中新的帧类型，并对这些新类型的使用作了一些测试。
New types of frames in H263 + and their testing are introduced.
介绍了H263 +中新的帧类型，并对这些新类型的使用作了一些测试。
New types of frames in H263 + and their testing are introduced.
应用推荐