![Your Instructor ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Andere mochten auch (19)
Ähnlich wie Ch14
Ähnlich wie Ch14 (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Ch14
- 11. Chapter 1 : Fundamentals of Testing
- 33. Find-Debug-Confirm Testing Debugging Developer 7.Is the problem fixed? Does the system now pass the same test it failed before? Does the test of the system still behave properly? 1. Can I reproduce the failure? 2. Does the failure indicate a test bug or a system bug? 3. What factors influence the failure? 4. What is the root cause of the failure? 5. How can I repair the defect without introducing new problems? 6. Is my fix properly debugged? Tester Tester Test Team Bug Report Clear handoffs and Division of Labor T hrough Bug Reporting A nd Test Release Process Bug Fix Development Team
- 46. Five components with bug counts of less that 60 each.
- 48. 그림
- 53. These two pictures compare efficiencies of the top 11 bug-finding test suites (out of 27). The top graph shows the first time the set of test suites was run. The bottom graph shows the results for the fifth time that same set of test suites was run. T he average test suite efficiency in the first pass, 0.4, is used as the axis crossing point in both graphs. With one exception, the same test suites are in the top 11 test suites, which shows bug clustering again. However, all test suites are less effective after five executions.