Đối tượng đọc giả Kiểm thử Phần mềm Máy tính: Các chuyên viên và Quản lý kiểm thử. Các nhà quản lý dự án sẽ thấu hiểu lịch trình, chiều sâu nghiên cứu và chất lượng của việc trao đổi thông tin. Lập trình viên hiểu rõ nguồn gốc của các lỗi phần mềm trong lúc lập trình, thấu hiểu các kiểm tra mà sản phẩm của họ phải vượt qua, và tại sao các chuyên gia kiểm thử làm việc họ đang làm. Các sinh viên . | Imagine finding an error fixing it then repeating the test that exposed the problem in the first place. This is a regression test. Added variations on the initial test to make sure that the fix works are also considered part of the regression test series. Under this usage regression testing is done to make sure that a fix does what it s supposed to do. Some programming groups create a set of regression tests that includes every fixed bug ever reported by any customer. Every time the program is changed in any way all old fixes are retested. This reflects the vulnerability of code fixes which unless they re well documented often don t look right when you read the code to later changes especially by new programmers. Imagine making the same fix and testing it but then executing a standard series of tests to make sure that the change didn t disturb anything else. This too is called regression testing but it tests the overall integrity of the program not the success of software fixes. Stub and driveT programs developed during incremental testing can be the basis of an automated regression test battery. Or you can create an automated regression suite of black box tests using a capture replay program discussed in Chapter 11 Automated acceptance and regression Tests . Both types of tests should be executed whenever errors are fixed. Someone talking about regression testing after bug fixing often means both. BUCK BOX TESTING When coding is finished the program goes to the Testing Group for further testing. You will find and report errors and get a new version for testing. It will have old errors that you didn t find before and it will have new errors. Martin McClure 1983 summarize data collected by Boehm on the probability of bug fixes working The probability of changing the program correctly on the first try is only 50 if the change involves ten or fewer source statements. The probability of changing the program correctly on the first try is only 20 if the change involves
