只运行测试的子集去掉了“做一些有价值的事情”的兴奋感觉，这是运行整个回归套件的传统实践提供的感觉。
To only run a subset of the tests removes that warm feeling of "doing something valuable," which the traditional practice of running the entire regression suite provides.
您可以有信心地做这件事，因为可以运行测试来证实您没有破坏任何事物。
You can do that with confidence because you have a test to run to confirm you didn't break anything.
注意，如果多个计数函数或测试在同一列上运行，那么排序与计数操作仅需做一次。
Note that if several counting functions or tests operate on the same column, then the sort and count operations only need to be done once.
这样做的目的是为了让您能继续使用Rake命令迁移数据库、运行测试等等。
The purpose of this to enable you to still use the Rake commands to migrate your database, run your tests, and so on.
通过这样做，他们将能够运行或者基于测试阶段或者基于横跨特定版本的更高层级的报告。
By doing this, they will be able to run reports based either on the test phase or at a higher level across the specific version.
如果您依赖它，那么在安装或初始化期间运行小测试来确保它能正确工作，这样做将是明智的。
If you depend on it, it's wise to run a small test during installation or initialization to make sure it works correctly.
总之，这种绑定是我看到的运行最好的一种—但那也只是反映在我做测试的版本上。
Overall, this binding was the best behaved one I looked at — but that just reflects the version I tested on.
如果这样做，则会自动导出所有测试函数并通过下面的代码运行它们。
If you do this, all your test functions will be automatically exported and run via the test function shown below.
因为Jester重新编译代码基，而且要为自己做的每个修改都重新运行测试套件，所以它的运行要比Clover这样的传统工具慢得多。
Because Jester recompiles the code base and reruns the test suite for each change it makes, it runs orders of magnitude more slowly than more traditional tools like Clover.
要加快这些测试套件，以便程序员可以更加经常地运行它们，您可以做的就是减少bug。
Anything you can do to speed up these test suites so programmers run them more often will reduce bugs.
您必须做的最后一件事情，便是确保运行来自Rational QualityManager的测试正常运行。
The last thing that you must do to make sure that things are working is to run your test from Rational Quality Manager.
你能够创建Web测试和单元测试并且一起运行在多台机器上做性能测试。
You can create web tests and unit tests and run them together under load across multiple machines.
这样做可以确保在单元测试运行之前，使用新的run - groovyc目标编译groovy脚本。
Doing so ensures the groovy scripts will be compiled with the new run-groovyc goal before any unit tests are run.
我的问题是，做单元测试项目运行在与过程，如果是这样的话，做这些加载的程序集堆起来呢？
My question is, do unit test projects run under the VS process and if so, do these loaded assemblies pile up?
我们接受这个数字，用它运行，同时尝试着在各种情况下对它进行测试，我们发现这样做非常有效。
We took that number and ran with it, and tried to test it in various scenarios, and we have found it's very effective.
虽然很多测试值得被自动化、但对于那些只运行一两次的测试，这样做并不划算。
Many tests will be worth automating, but for all the tests that you run only once or twice, this approach is inefficient.
同时，在任何情况下，推荐的工作因为这是做ut的环境，与自己的数据库tfs代理运行构建和运行测试不碰任何关键数据。
Also, in any case, the recommended work for this is do an environment for ut, with your own database in order the TFS Agent runs a build and run the test without touching any critical data.
同时，在任何情况下，推荐的工作因为这是做ut的环境，与自己的数据库tfs代理运行构建和运行测试不碰任何关键数据。
Also, in any case, the recommended work for this is do an environment for ut, with your own database in order the TFS Agent runs a build and run the test without touching any critical data.
应用推荐