软件测试与评估：07-Achieve Acceptable Mission.pptVIP

Principles of Software Testing for TestersModule 7: Achieve Acceptable Mission Module 7 - Content OutlineDefinition of the workflow: Achieve Acceptable MissionReporting the status of testing Review: Where We’ve BeenIn the last two modules, we covered the workflow detailTest and EvaluateIn part one, we looked at techniques for implementing tests, and in part two, we looked at analyzing failures and writing change requests. Achieve an Acceptable MissionIn this module, we’ll look at monitoring that the Mission is being achieved and reporting the status of the test effort Achieve an Acceptable MissionThis module focuses on Assessment of the test effort reporting an evaluation summary of the test resultsIn the last module, we discussed change requests which are used here to help evaluate status.We will look mainly at producing Evaluation Summaries. Module 7 - Content OutlineDefinition of the workflow: Achieve Acceptable MissionReporting the status of testing Discussion Exercise 7.1: Reporting StatusPick a project and a point in time.You are the test manager.The project manager asks you:How far are you with testing?How much do you have left to do?How do you answer? Status ReportingKey questions: How far are we? How much is left to do?Experienced test managers have very different answersComplex, multidimensional questionMany types of data explain “extent of testing”Simple metrics are often profoundly misleadingThe best status reports consider several dimensions togetherEight different categories of information Dimensions of “Extent of Testing”Product We’ve tested 80% of the lines of code.PlanWe’ve run 80% of the test cases that we had planned to run.ResultsWe’ve discovered 593 bugs.EffortWe’ve worked 80 hours a week on this for 4 months. We’ve run 7,243 tests.Common answers are based on the: Dimensions of “Extent of Testing”Obstacles We’ve been plugging away but we can’t be efficient until X, Y, and Z are dealt with.RisksWe’re getting a lot of complaints fro