a332897696
码龄13年
翻译：
A test case is a detailed procedure that fully tests a feature or an aspect of a feature.
一个测试用例是测试一个特性或者特性的一个方面的详细步骤。
Whereas the test plan describes what to test, a test case describes how to perform a particular test.
一个测试计划描述了要测的内容，一个测试用例描述了怎么样详细的去展开测试
You need to develop a test case for each test listed in the test plan. Figure 2.10 illustrates the point at which test case design occurs in the lab development and testing process.....
你需要去列出一个测试计划中每一个需要测试的点。图2.10
A test case is a detailed procedure that fully tests a feature or an aspect of a feature. Whereas the test plan describes what to test, a test case describes how to perform a particular test. You need to develop a test case for each test listed in the test plan. Figure 2.10 illustrates the point at which test case design occurs in the lab development and testing process.
designing
A test case includes:
一个测试用例包括
The purpose of the test.
测试的目的
Special hardware requirements, such as a modem.
特殊的硬件要求，比如一个器件
Special software requirements, such as a tool.
特殊的软件要求，比如一个工具
Specific setup or configuration requirements.
特殊的配置或者设置要求
A description of how to perform the test.
The expected results or success criteria for the test.
一个如何进行测试的描述
还有测试的期望结果或者成功标准
Test cases should be written by a team member who understands the function or technology being tested, and each test case should be submitted for peer review.
测试用例应该由理解这个功能或者技术的人来写，然后每一个测试用例都应该被提交给每一个人看到评审
Organizations take a variety of approaches to documenting test cases; these range from developing detailed, recipe-like steps to writing general descriptions.
组织采用很多种方法去记录测试用例，这些范围从详细的开发 类似配方的步骤到编写总的描述。
In detailed test cases, the steps describe exactly how to perform the test. In descriptive test cases, the tester decides at the time of the test how to perform the test and what data to use.
在详细的测试用例中，这些步骤确切的描述了怎么样进行测试。在描述性的测试用例中 测试者在测试中决定怎么样去进行测试和用什么数据去进行测试。
Most organizations prefer detailed test cases because determining pass or fail criteria is usually easier with this type of case.
多数组织者更喜欢详细的测试用例因为对于这种类型的用例 决定通过还是失败的标准是更容易的
In addition, detailed test cases are reproducible and are easier to automate than descriptive test cases.
另外 详细的测试用例是每一步骤清晰可见的，也比描述性的测试用例更容易自动化
This is particularly important if you plan to compare the results of tests over time, such as when you are optimizing configurations.
如果你计划在一段时间内去比较测试的结果这是尤为重要的，比如当你正在优化配置时。
Detailed test cases are more time-consuming to develop and maintain. On the other hand, test cases that are open to interpretation are not repeatable and can require debugging, consuming time that would be better spent on testing.
（这一块不懂）
详细的测试用例是更花费时间去开发和维护的。另一方面，测试用例是更加开放的去打断的不是重复性的和可以要求的debug的，花费时间在测试上可能会更好
Test Case Design
测试用例设计
Test Case ID:
测试用例编号
It is unique number given to test case in order to be identified.
这是给测试用例的唯一编号为了区分
Test description:
测试描述
The description if test case you are going to test.
你将要进行测试的测试用例的描述
修订历史:
Each test case has to have its revision history in order to know when and by whom it is created or modified.
每一个测试用例都必须有它自己的修订历史为了知道什么时候谁来创建和修改的
Function to be tested:
The name of function to be tested.
要测试的功能
功能的名字被测试
Environment:
It tells in which environment you are testing.
环境：它告诉你在哪个环境进行测试
Test Setup:
Anything you need to set up outside of your application for example printers, network and so on.
测试安装程序
每一个你需要设置在你的应用程序外的任何内容，比如打印机、网络等等
Test Execution:
测试执行
It is detailed description of every step of execution.
每一步执行的步骤的详尽描述
Expected Results:
The description of what you expect the function to do.
预期结果:
描述期望功能去做什么
Actual Results:
实际结果：
pass / failed
通过/失败
If pass - What actually happen when you run the test.
如果是通过-是你跑这个测试的时候实际发生的事情
If failed - put in description of what you've observed.
如果是失败-把你观察到的描述写进去
