SG 3 Perform Non-functional Test Analysis and Design
执行非功能测试分析和设计
During test analysis and design the test approach for non-functional testing is translated into tangible test conditions and test cases.
在测试分析和设计中,非功能测试测试方法被转化为真实的测试条件和测试用例
SP 3.1 Identify and prioritize non-functional test conditions
明确和分级非功能测试条件
Test conditions are identified and prioritized, based on an analysis of the non-functional features as specified in the test basis. Example work products 1. Test basis issue log 2. Non-functional test conditions 3. Non-functional test design specification Sub-practices 1. Study and analyze the test basis (such as non-functional requirements, architecture, design and interface specifications) 2. Discuss issues regarding the test basis with the document owner 3. Derive the test conditions from the test basis according to the documented non-functional test approach 4. Prioritize the test conditions based on identified product risks 5. Document the test conditions in a test design specification based on the test design specification standard Examples of elements of a test design specification include the following [after IEEE 829]: Test design specification identifier Features (and/or items) to be tested Approach refinements Test conditions Pass/fail criteria 6. Review the test design specifications with stakeholders 7. Revise the test design specifications and test conditions as appropriate, e.g., whenever the requirements change
测试条件被明确和优先级分类,基于测试原则中指出的非功能特点的分析。
例子工作产品:1. 测试基本问题日志。2非功能测试条件。3. 非功能测试设计说明书
子实践:1. 学习和分析测试原则。2. 讨论测试原则关联的问题。3.驱动测试条件从测试基准,根据文档化的非功能测试方法。4.优先级分类测试条件,根据产品风险。5.文档化测试条件到一个测试设计说明书。基于测试设计说明书。6.重审测试设计说明书。
SP 3.2 Identify and prioritize non-functional test cases
明确和优先级分类非功能测试用例
Non-functional test cases are identified and prioritized to address the defined test conditions. Example work products 1. Non-functional test cases 2. Non-functional test case specification Sub-practices 1. Derive the test cases from the test conditions according to the documented non-functional test approach. 2. Prioritize the test cases based on identified non-functional product risks 3. Document the non-functional test cases in a test case specification based on the test case specification standardExamples of elements of a test case specification include the following [IEEE 829]: Test case specification identifier Features (and/or items) to be tested Input specifications Output specifications Environmental needs Special procedural requirements Inter-case dependencies 4. Review the test case specifications with stakeholders 5. Revise the test case specifications as appropriate
非功能测试用例被明确和优先级分类来促进测试条件的定义。
例子工作产品:非功能测试用例,非功能测试用例说明书。
子实践:1。从测试条件中提取测试用例,根据文档化的非功能测试方法。2. 优先级分类测试用例,基于测试用例说明书。3.文档化非功能性测试。包括:测试用例说明书标识符。要测试的特点,输入说明书,输出说明书,需要的环境,需要的特定过程,用例之间的依赖。4.重审测试用例说明书。实时修改。
SP 3.3 Identify necessary specific test data明确必须的指定测试数据
Specific test data necessary to support the non-functional test conditions and test cases is identified. Example work products 1. Test data specification Sub-practices 1. Identify and specify the necessary specific test data required to implement and execute the nonfunctional test cases 2. Document the necessary specific test data, possibly as part of the test case specification
特定的测试数据是必须的用来支持非功能测试条件和测试用例被明确。
例子工作产品:测试数据文档
子实践:1.明确和指出必须的特定测试数据,需要执行和实施非功能测试用。。2. 文档化必须的特定测试数据。可能是测试用例说明书的一部分。
SP 3.4 Maintain horizontal traceability with non-functional requirements
维护非功能需求水平可追溯
Traceability between the non-functional requirements and the non-functional test conditions is established and maintained. Example work products 1. Non-functional requirements / test conditions traceability matrix Sub-practices 1. Maintain non-functional requirements traceability to ensure that the source of non-functional test conditions is documented 2. Generate a non-functional requirements / test conditions traceability matrix 3. Set up the traceability matrix such that monitoring of non-functional requirements coverage during test execution is facilitated
非功能需求和非功能测试条件的追溯性被建立和维护。
例子工作产品:1.非功能需求,非功能测试条件追溯矩阵。
子实践:1. 维护非功能需求可追溯来保证非功能条件的来源被文档化。2. 产生非功能需求,条件可追溯矩阵。3.建立可追溯矩阵,在测试执行中监视非功能需求覆盖率被促进