TMMI_测试过程改进框架_已定义级别6_非功能测试6

SG 5 Perform Non-functional Test Execution

执行非功能测试实施

Non-functional tests are executed according to previously specified test procedures. Incidents are reported and test logs are written.

非功能测试被执行，根据之前制定的测试步骤，事故被报告，测试日志被书写。

SP 5.1 Execute non-functional test cases

执行非功能测试用例。

The non-functional test cases are executed manually using documented test procedures and/or automatically using test scripts. Example work products 1. Test results Sub-practices 1. Execute the non-functional test cases using documented test procedures and/or test scripts 2. Record actual results 3. Compare actual results with expected results 4. Repeat non-functional test activities as a result of an action for an incident found by performing retesting (confirmation testing) 5. Perform non-functional regression testing as appropriate.Note that some non-functional testing will be conducted informally without using pre-defined detailed test procedures, e.g., a heuristic evaluation to test the usability. Note that the non-functional test execution is normally preceded by the overall intake test. Refer to the practices SP 2.3 Specify intake test procedure and SP 3.1 Perform intake test from the process area Test Design and Execution for more details on the intake test on the test object, and to the practice SP 2.4 Perform test environment intake test from the process area Test Environment for more details on the intake test on the test environment.

非功能测试用例被执行，手动测试使用文档化的测试过程和自动测试使用测试脚本。

例子工作产品：1.测试结果

子实践：1.执行非功能测试用例，使用文档化的测试过程或者测试脚本。2.记录实际结果。3.比较实际结果和期望结果。4.重复非功能测试行为，由于执行测试发现的事故。5.适当的执行非功能回归测试。备注，有些非功能测试被执行不正式的，没有使用预定义的详细测试过程。

SP 5.2 Report test incidents报告测试事故

Differences between actual and expected results are reported as non-functional test incidents. Example work products 1. Non-functional test incident reports Sub-practices 1. Log non-functional test incidents when a discrepancy is observed 2. Analyze the non-functional test incident for further information on the problem 3. Establish the cause of the non-functional test incident, e.g., system under test, test documentation, test data or test execution mistake 4. Assign an initial priority and severity level to the non-functional test incident 5. Formally report the test incident using an incident classification scheme Examples of elements of a test incident report include the following [IEEE 829]:  Test incident report identifier  Summary  Incident description (input, expected results, actual results, anomalies, date and time, test procedure step, environment, attempts to repeat, testers, observers)  Priority level  Severity level 6. Review the non-functional test incident report with stakeholders 7. Store non-functional test incidents in a central repository Refer to the goal SG 4 Manage test incidents to closure from the process area Test Design and Execution for more details on how test incidents are processed and managed to closure.

实际和期望结果之间的差别别报告为非功能测试事故。

例子工作产品：1.非功能测试事故报告。

子实践：1. 记录非功能测试事故日志，当背离被发现的时候。2. 分析非功能测试事故。3.建立非功能测试事故的来源。比如，测试系统，测试文档，测试数据，执行错误。4.为非功能测试事故分配初始优先级和严重级别。5.正式的报告测试事故使用事故分类计划。例子：测试事故报告标识符，概要，事故描述，优先级，严重级别。6.重审非功能测试事故报告。7.保存非功能测试事故到中央存储。

SP 5.3 Write test log 写测试日志

Test logs are written to provide a chronological record of relevant details about the execution of the non-functional tests. Example work products 1. Test logs Sub-practices 1. Collect test execution data 2. Document the test execution data by means of a test log, based on the test log standard Examples of elements of a test log include the following [IEEE 829]:  Test log identifier  Description (items being tested, environment in which the testing has been executed)  Activity and event entries (execution description, test results, anomalous events, incident report identifiers)3. Review the test log with stakeholders

测试日志被书写来提供一个连贯的关联执行非功能测试细节的记录。

例子工作产品：1.测试日志

子实践：搜集测试执行数据，文档化测试执行数据，通过测试日志，基于测试日志标准。包括：测试日志标识符，描述。行为和实践入口。重审测试日志。