测试计划：
与任何项目一样，测试也应该由计划驱动。测试计划为整个测试项目的执行和跟踪生成报告。
准备测试计划
- 什么需要测试——测试的范围，包括明确哪些将被测试，哪些不会被测试。
- 将如何执行测试——将测试分解为可管理的小任务，并确定用于执行任务的策略。
- 测试所需资源
- 执行测试活动的时间表。
- 以上所有可能面临的风险，有适当的缓解和应急计划。
测试用例规范：
- 以测试计划为基础，测试团队设计测试用例规范，然后成为准备单个测试用例的基础。
- 测试用例只不过是在产品上执行的一系列步骤，使用一组预定义的输入数据，期望在给定的环境中产生一组预定义的输出。
- 它描述了“如何”实现这些测试用例
- 测试用例规范很有用，因为它列出了项目的规范细节。
每个规格的详细信息：
| Test Case Specification | Description |
|---|---|
| Test Case ID(TC_ID) | Unique ID to identify/report the bug if present in the functionality of software |
| Test Case Objective | The purpose of the test. The lists can be generated to perform intended task, for which software is developed. Results should always follow the test case objective |
| Pre-requisite | This can include environment setup, supporting software environment setup. for the project, or any fields in which user will give the input. So that test cases can be planned accordingly. |
| Steps | This includes steps to be performed to give the input to the system, so that system can perform its specified task and display the result accordingly. If automated testing is used, then, these steps are translated to the scripting language of the tool. |
| Input Data | The choice of input data will be depended on the test case itself and the technique followed in the test case. For e.g. equivalence partitioning, boundary value analysis etc. |
| Expected Result | It can be the user required output to be shown |
| Actual Result | This step should do a comparison of the expected and actual results to highlight any differences. |
| Status | Whether expected results and actual result match, if it matches then PASS or else FAIL |
例子：
为给定的软件生成测试用例报告
注意：可以看出，Viginere 密码的状态为 FAIL，因为预期结果不等于实际结果
该测试报告可以向经理/利益相关者/客户提供有关产品的清晰图片，并可以检查项目的质量。