我要补充一点关于单元级和系统级测试的内容：明智的项目和企业会进行测试数据管理。
One thing I'll add about both unit - and system-level tests: Smart projects and organizations will spend some effort on test data management.
首先我要介绍的是如何安装和测试一个新的shell，以及如何改变默认的shell。
The first thing I need to cover is how to install and test a new shell, and how to change the default shell.
速度：我测试的每部机器上，Windows7的运行速度都很快，延迟现象也比Vista上常见到的要少的多。
Speed: In my tests, on every machine, Windows 7 ran swiftly and with far fewer of the delays typical in running Vista.
如果您将在六、七个月后部署，那么我敢说使用它是安全的，当然，在生产部署前要进行适当的测试。
If you're looking at deployments in 6-7 months from now, then I would say it is safe to proceed, with, of course, appropriate testing prior to a production deployment.
因此，我要针对感兴趣的边界条件编写几个测试，见清单4。
To that end, I'm going to add a few tests for interesting boundary conditions, shown in Listing 4.
然而，由于多种原因(例如，因为它不是最终代码，所以当要升级到更新版本时，删除它可能会导致某些问题)，我建议您把它安装在测试机器上。
However, I recommend that you use a test machine for installation for various reasons (for example, since it's not final code, removing it might lead to problems when upgrading to a later version).
这个失败很容易理解，但我不确定是不是真的要“修正”它——我没有测试的这个方法非常微不足道，为这么微不足道的方法添加测试有点浪费精力。
This failure is easy to understand, but I'm not sure I really want to "fix" it — the method I'm not testing is trivial, and adding tests for trivial methods can be a waste of effort.
我决定使用概念来表示页面，因为我知道，我要通过它们产生更抽象的测试概念，并且我想要保持这种一致。
I decided to use concepts to represent pages because I knew that I would generate the more abstract test concepts from them and that I wanted to maintain this alignment.
注意，在这个描述中，我的意图只是想帮助那些要监测或测试客户端/服务器端交互的工具和框架，当然不是要模仿WSDL或WADL。
Note that my intent in this description is only to help tools and frameworks that want to monitor or test client-server interactions, but certainly not to mimic WSDL or WADL.
客户经常让我给他们的管理层解释为什么我们要进行用户测试，为什么我们要花更多时间测试网站原型而不是已实现的网站。
Clients often ask me to explain to their boards why we're running user tests. And why we spend our time user testing mock-ups, rather than the finished website.
我做这么一次异想天开的旅行，其核心是要测试一下一种哲学理念：人生体验比随身携带的东西更加重要。
At the heart of my whimsical journey was an experiment that would test out a more philosophical idea: that what we experience in life is more important than what we bring with us.
为了可以简单地测试要开发的模块的速度提高情况，我编写了一个简单的测试程序来运行不同版本的模块。
To easily test the speed of the incrementally improving modules I planned to develop, I wrote a small test harness to run different versions of the module.
要测试此过程，我上传了几张我和我家人的圣诞照片，然后转到list . php页面。
To test this process, I uploaded a couple of Christmas shots of myself and my family, then went to the list.php page.
公平地讲，我在自动化测试方面花费了比我预计要多很多的时间，这是因为我选择了要了解JUnit。
In all fairness, I spent more time on automated tests than I could have because I chose to learn JUnit.
不过我测试的Edge配置更昂贵，比基本款电池要大，所以基本款的续航时间可能只有我所测试的三分之二。
But the costlier Edge configuration I tested had a larger battery than the base unit, so would likely last only two-thirds as long.
在我的测试中，虚表上的查询比做同样查询的TimeSeries函数要慢一个数量级。
In my tests, it can be an order of magnitude slower than a TimeSeries function that does the same query.
对于文章的大部分示例，我将使用一种名为HTMLDocumentEditor的免费功能性HTML编辑器，将其作为要测试的应用程序(参见参考资料)。
For most of the article's examples, I'll use a free, functional HTML editor called HTMLDocumentEditor as an application to test (see Resources).
现在mock准备好了，我把它作为参数传递给要测试的方法。
Now that the mock is prepared, I pass it as an argument to the method under test.
要运行该测试，我需要生成项目，在NUnit应用程序中打开生成的程序集，然后单击Run按钮。
To run this test, I'll need to build the project, open the generated assembly in the NUnit application, and then click the run button.
这个冗长的目标(相信我，我还见过冗长得多的目标)要执行四个不同的过程：编译源代码、编译测试、运行JUnit测试和创建一个JUnitReport。
This long target (believe me, I've seen much longer ones) is performing four distinct processes: compiling source, compiling tests, running JUnit tests, and creating a JUnitReport.
我有一些坏消息要告诉你：即使最复杂的测试也存在很大的缺陷。
I have some bad news for you: Even the most sophisticated tests have considerable flaws.
我只是要确定，我所开始的这次额外备份在其完成之后，会使用外部驱动来进行一次测试启动，这就确保了如果事情出现了严重错误的话，我会有一种很容易就返回到Snow Leopard中的手段。
Just to be sure I kicked off an extra backup and once done did a test boot using the external drive to ensure I had an easy return path to Snow Leopard if things went badly wrong.
小女孩说，“我来这里做血液测试，而他们要割我的手指头。”
"I'm here for a blood test, and they're going to cut my finger," said the girl.
我很伤心，所以我要更努力学习，找到一个好的学习方法，测试虽然不好但我不会放弃。
I am very sad, so I want to study more hard, find a good method of study, although the test is bad but I won't give up.
我要提醒你们，下周23号将会有个周期表测试。
A remember about the Periodic Table test which will be added next week on the 23rd.
我来这里做血液测试，他们要切我的手指。
I'm here for a blood test, and they 're going to cut my finger.
（例如，考虑一下，设计1风格中的测试套件：要确保所有用户界面控件在更改后的测试中被涉及是一件多么困难的事情?）长期以来，这导致了我称为“测试套件变质”的问题，完整的测试套件仍旧在运行，但什么也测试不了。
Will the tester even know that's a goal of the suite?) Over time, this leads to what I call "test suite decay, " in which a suite full of tests runs but no longer tests much of anything at all.
他们要我来为耳塞做一下测试，因此我已经爽了数个礼拜了（真贱）。
They had me test a pair out, and I've been enjoying them for a couple weeks now.
他们要我来为耳塞做一下测试，因此我已经爽了数个礼拜了（真贱）。
They had me test a pair out, and I've been enjoying them for a couple weeks now.
应用推荐