要为非功能性需求的构建测试用例，测试人员要依赖于附加的文档，因此也称作需求补充说明。
To build test cases for non-functional requirements, testers are dependent upon supplemental documentation, also called supplementary specifications.
这些图的类型，有文本描述的补充说明，应该为功能验证测试团队在这个项目周期中工件测试用例提供充分的信息。
These types of diagrams, complemented by text descriptions, should provide sufficient information for the Function Verification Test team to build test cases very early in the project lifecycle.
接下来我们将说明构建测试用例的全过程。
测试和QA计划：详细说明测试和 QA 计划，并在其中包括测试用例。
Testing and QA plan: Details the testing and QA plans and includes test cases.
通过一个示范模块demo . doh，可以说明测试用例结构，该模块作为一个Dojo目录结构的对等模块。
The test case structure is illustrated by using a demonstration module, demo.doh, that is placed as a peer module to the Dojo directory structure.
RUP强调，规格说明和测试用例的执行可以是并行的活动，让我们讨论一下如何从一个TMap的观点来处理这个问题。
RUP stresses that specification and execution of test cases can be parallel activities. Let's discuss how to deal with this from a TMap point of view.
根据测试用例产生的依据可以将软件测试分为基于程序代码的测试和基于规格说明的测试两大类。
According to the source that is used to derive tests, software testing is classified into two categories -program based testing and specification based testing.
本文主要研究了基于UML状态图说明的测试用例生成技术。
In this paper, we studied the generation of testing cases based on UML statement diagram specification.
介绍了一种基于形式规格说明和分类树方法生成软件测试用例的方法。
An approach for generating test cases from formal specification and the classification-tree method is presented.
理论和实验结果说明，如果满足测试条件，它们保证全故障覆盖，且产生较少的测试用例。
Theory and experiments show that the cases suites guarantee full coverage and the methods generate less test cases if it satisfies some assumptions.
由软件的形式规格说明构造分类树，再把由分类树方法得到的测试用例转化为析取范式，进一步精炼测试用例。
Firstly, a classification-tree is constructed based on specification of the test object, and then test cases obtained from the classification-tree are refined by generating a disjunctive normal form.
本文提出了一种从形式规格说明中利用等价类划分的方法自动生成软件测试用例的算法，给出了算法步骤。
The paper puts forward an automated testing case generator algorithm which uses equivalence class division methods and formal specification.
“历史记录”选项卡中，键入“不再需要测试用例”以说明该手动测试用例已关闭的原因。
History TAB, type test case is No Longer Required to explain why the manual test case is closed.
这一阶段的目的是按照测试计划中的说明使测试策略变得更加精细，并且要确定测试用例、测试启动和测试软件需求。
The purpose of this phase is to specify refinements to the strategy as specified in the test plan and also to identify the test case, test setup and test software requirements.
本文研究了基于形式规格说明来生成有效测试用例的方法。
Then, the formal specification can be written according to the use case scenarios.
本文研究了基于形式规格说明来生成有效测试用例的方法。
Then, the formal specification can be written according to the use case scenarios.
应用推荐