SG 3 Perform Test Execution 执行测试执行
Tests are executed according to the previously specified test procedures and test schedule. Incidents are reported and test logs are written.
依据之前制定的测试流程和测试进度，测试被执行。意外被报告，测试日志被记录。
SP 3.1 Perform intake test 执行冒烟测试
Perform the intake test (confidence test) to decide whether the test object is ready for detailed and further testing. Example work products 1. Intake test log 2. Incident reports Sub-practices 1. Perform the intake test (confidence test) using the documented intake test procedure to decide if the test object is ready for detailed and further testing 2. Document the results of the intake test by means of a test log, based on the test log standard 3. Log incidents when a discrepancy is observed Note that this practice is highly related to the practice SP 2.4 Perform test environment intake test from the process area Test Environment. The intake test on the test object and test environment can possibly be combined.
执行冒烟测试来决定是否测试对象已经准备好了来做更详细的测试。例子工作产品：冒烟测试日志，意外报告
子实践：1.执行冒烟测试。2. 文档化冒烟测试结果。使用测试日志，基于测试日志标准。 3. 当矛盾发生时记录意外。
SP 3.2 Execute test cases 执行测试用例
According to the defined execution schedule, the test cases are run either manually using documented test procedures and/or via test automation using pre-defined test scripts. Example work products 1. Test results Sub-practices 1. Execute the test cases using documented test procedures and/or test scripts 2. Record actual results 3. Compare actual results with expected results 4. Repeat test activities after the receipt of a fix or change by performing re-testing (confirmation testing) 5. Perform regression testing as appropriate. Note that some testing will be carried out informally using no pre-defined detailed test procedures, e.g., during exploratory testing or error guessing.
根据已定义的执行进度，测试用例被运行要不使用手动测试，要不使用自动化测试。
例子工作产品：测试结果。
子实践：1.执行测试用例2. 记录实际结果。3比较实际结果和期望结果。4.在修复和改变之后重复测试行为，通过执行再次测试。 5执行回归测试。
SP 3.3 Report test incidents 报告测试事故
Discrepancies between the actual and expected results are reported as test incidents. Example work products 1. Test incident reports Sub-practices 1. Log test incidents when a discrepancy is observed. 2. Analyze the test incident for further information on the problem 3. Establish the cause of the test incident, e.g., system under test, test documentation, test data, test environment or test execution mistake 4. Assign an initial priority and severity level to the 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 test incident report with stakeholders 7. Store the test incidents in a central repository
真实和期望的结果之间的矛盾。
例子工作产品： 测试意外报告
子实践：1，当矛盾产生的时候，记录测试意外。2分析测试意外，从而得到更多的关于问题的信息。 3.找到测试事故的原因。 例如，系统测试，测试文档，测试数据，测试环境，测试执行错误。 4. 分配测试事故的优先等级和严重性。 5. 报告测试事故。6. 重审测试事故报告。 7.保存测试事故在一个中央仓库。（svn）
SP 3.4 Write test log 写测试日志
Test logs are written to provide a chronological record of relevant details about the execution of the 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. 测试日志
子实践：1.搜集测试执行数据。 2.文档化测试执行数据，通过测试日志，
测试日志包含下面几个东东： 测试日志标识符，描述。行为和实践标准。重审测试日志