软件测试与评估：06-Analyze Test Failures.pptVIP

Principles of Software Testing for TestersModule 6: Analyze Test Failures Module 6 ObjectivesThis continues the workflow: Test EvaluateModule 5 focused on TestThis Module 6 focuses Evaluate Review: Where We’ve BeenIn the last module, we covered part of the Test and Evaluate workflow detail. We focused on what techniques to use to implement appropriate tests Test and Evaluate – Part Two: EvaluateIn this module, we look at the Evaluate part of this work with the questions:How will you evaluate your test results?How will you report your findings? Test and Evaluate – Part Two: EvaluateThis module focuses on the activity Analyze Test Failures In the last module, we covered Implement Test using different techniquesWe will spend a lot of time on Change Requests, as they are the product of this activity Review: Definition of QualityIn Module 2, we looked at definitions of QualityQuality as fitness for use, determined by both customer satisfiers and dissatisfiers -- Dr. Joseph M. JuranQuality as value to some person-- Gerald M. WeinbergHere we look at Analyzing Test ResultsA bug report is a report that some aspect of the product appears to unnecessarily reduce its valueTesters (and others) may criticize design decisions -- the code may not be defective, the product is just unnecessarily clumsyEffective communication is a key part of this activity. Some Preliminary DefinitionsIn this module, the following terms are used:Change request: any report of an incident, defect or potential enhancement, that is intended as a request for a change to the software under developmentDefect report: a change request reporting a (suspected) defect or error in the productBug: some aspect of the product under test, that in the eyes a stakeholder, unnecessarily reduces its value; possibly a suspected defectIn this module, no specific review process for change requests is assumed Module 6 AgendaAdvocate repairing the important problemsInvestigate problems effectivelyWrite good change requests