G. Rothermel and M. Harrold. Analyzing regression test selection techniques. IEEE Trans. on Softw. Eng., 22(8):529--551, Aug. 1996.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....same initial state and inputs, the sequential program will deterministically produce the same output on repeated executions, even in the presence of systematic faults [94] or in the presence of intrusive probes. Reproducibility is essential when performing regression testing or cyclic debugging [92][96] where the same test cases are run repeatedly with the intent to validate that either an error correction had the desired effect, or simply to make it possible to find the error when a failure has been observed [59] or to show that no new errors have been introduced when correcting another ....

....necessary and sufficient conditions for a set of behaviors to deterministically occur. A system is partially reproducible if we can deterministically observe it but only control some of the necessary and sufficient conditions. Reproducibility is a necessity when debugging, when regression testing [92], or when sufficient coverage during testing is sought (we will in section 4.5, chapter 5 and section 6.4.4 elaborate on this) Contributions . In this chapter we present a software based method for deterministic observations of single tasking, multi tasking, and distributed real time systems. ....

Rothermel G. and Harrold M.J. Analyzing regression test selection techniques. IEEE trans. Software Engineering. 8(22):529-551. August 1996.

....12 balanceAfter = balanceAfter ; 13 14 15 16 class account 17 private double balance; 18 private double limit; 19 private transaction[ t; 20 private int idx; 21 private double ic, id1, id2; 22 23 public account( 24 balance = 0. 0; 25 limit = 500.0; 26 t = new transaction[20]; 27 idx = 0; 28 ic = 0.05; 29 id1 = 0.1; 30 id2 = 0.2; 31 32 33 public void deposit(double amount) 34 balance = amount; 35 t[idx ] new transaction( Deposit , 36 amount, balance) 37 38 39 public void withdraw(double amount) 40 if (balance = limit) 41 balance = ....

....called selective regression testing, is to select those test cases from a given test suite covering changed parts of the program. There are various techniques applying different strategies for selecting test cases. A comparison of methods following the selective retest strategy can be found in [20]. Unfortunately, all selective regression testing techniques are white box techniques to our knowledge, i.e. they do not consider specification changes. The tool we have implemented for regression testing uses a modified version of the selective regression testing technique proposed by Rothermel ....

G. Rothermel and M. J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, Aug. 1996.

.... paths [18, 25] Our research concerns the automation of test data generation based on the white box approach and symbolic execution [14, 4, 5] The presented approach could be used to generate regression test data which is an expensive maintenance process directed at validating modified software [22]. 1 DRAFT A detailed review of the literature concerning test data generation can be found in [16] In this paper, we will present our approach to test data generation (section 2) The experimental phase of our research will be presented in section 3 and will afterwards be discussed in section ....

G. Rothermel and M. J. Harrold. "Analyzing regression test selection techniques", IEEE Trans. Soft. Eng., aug. 1996, pp.529--551.

....Selective retest techniques attempt to strike 14 a balance between test eciency and cost. They are also used to nd tests that need to be updated or added to the test suite for the modi ed program. Rothermel and Harrold analyze the di erent techniques and provide a framework for evaluating them [15]. Automatic test execution is described in several testing books [10, 4] 2.3 Test evaluation Test evaluation consist of two phases; checking the pass fail status of each individual test case, and then checking whether the test cases are deemed to be sucient to assure the tester that the ....

Gregg Rothermel and Mary Jean Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8), August 1996.

....whole system after each modi cation is considered expensive and time consuming. Therefore, it is important to re synthesize the modi ed parts of service speci cation in order to reduce the maintenance cost, which was reported to account for as much as two thirds of the cost of software production [30]. In this paper, we present a new method for re synthesizing the protocol speci cation from a modi ed service speci cation. The method consists of a set of rules that would be applied to di erent PE s after a modi cation to the service speci cation, in order to produce new synthesized (henceforth ....

G. Rothermel and M. J. Harrold, \Analyzing Regression Test Selection Techniques, " IEEE Trans. on Software Engineering, Vol. 22, No. 8, pp. 529-551, 1996.

.... criteria such as branch or dataflow coverage of the portions of the code that are considered directly or indirectly affected by the code changes (Ostrand and Weyuker, 1988; Harrold and Soffa, 1988; Agrawal et al. 1988; Rothermel and Harrold, 1994b; Kung et al. 1996; Rothermel and Harrold, 1993; Rothermel and Harrold, 1996; Binkley, 1997) Fewer researchers have been concerned with gray box and black box regression testing (von Mayrhauser et al. 1994a; Leung and White, 1990; Leung, 1995) Here, changes related to the functionality of a system are regression tested. With the advent of more and more systems with a ....

....the time and effort of regression testing while preserving the efficacy of the test suite in revealing faults. For either strategy, the tester may need to develop new tests to exercise new features of the software or to cover parts of the software that are no longer covered by existing tests. (Rothermel and Harrold, 1996) provide a definition of regression testing as consisting of the following steps: 1. Identify changes. 2. Determine which of the currently existing test cases will remain valid for the new version of the software (Eliminate all tests that are no longer applicable this results in a set of ....

[Article contains additional citation context not shown here]

Rothermel, G. and Harrold, M. J. (1996) `Analyzing regression test selection techniques', IEEE Transactions on Software Engineering, 22(8), 529--551.

.... selection approaches attempt to reduce the cost of regression testing by selecting some appropriate subset of the existing test suite [3, 22, 28] Test selection techniques normally use the source code of a program to determine which tests should be executed during the regression testing stage [21]. Test case prioritization techniques attempt to order a regression test suite so that those tests with the highest priority, according to some established criterion, are executed earlier in the regression testing process that those with lower priority [9, 24] By prioritizing the execution of a ....

....execution of a regression test suite. Finally, Section 5 explores the design and implementation details of Joshua and Section 6 notes future research and development avenues. 2 Regression Testing Background 2. 1 Notation For simplicity, we adopt the regression testing notation used throughout [21]. We will brie y summarize this notation and extend it as needed throughout the remainder of this paper. We let P be a program and P 0 be a modi ed version of P . We use S to denote the speci cation for program P and S 0 to denote the speci cation for program P 0 . Furthermore, we let P (i) ....

[Article contains additional citation context not shown here]

G. Rothermel and M. J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529-551, August 1996.

No context found.

G. Rothermel and M. Harrold. Analyzing regression test selection techniques. IEEE Trans. Softw. Eng., 22(8):529--551, Aug. 1996.

No context found.

G. Rothermel and M. Harrold. Analyzing regression test selection techniques. IEEE Trans. Softw. Eng., 22(8):529--551, Aug. 1996.

No context found.

G. Rothermel and M. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, Aug. 1996.

No context found.

G. Rothermel and M.J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, August 1996.

No context found.

G. Rothermel and M. J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, Aug. 1996.

No context found.

G. Rothermel and M. Harrold. Analyzing regression test selection techniques. #### ###### ###### ####, 22(8):529-551, Aug. 1996.

No context found.

G. Rothermel and M.J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, August 1996.

No context found.

G. Rothermel and M. J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, August 1996.

No context found.

G. Rothermel and M. Harrold. Analyzing regression test selection techniques. IEEE Trans. Softw. Eng., 22(8):529--551, Aug. 1996.

No context found.

G. Rothermel and M.J. Harrold. Analyzing regression test selection techniques. IEEE Trans. Softw. Eng., 22(8):529--551, August 1996.

....all technique can be expensive: rerunning all test cases may require an unacceptable amount of time or human e ort. Regression test selection (RTS) techniques [5, 17, 26] use information about P , P , and T to select a subset of T with which to test P . For a survey of RTS techniques, see [25]. Empirical studies of some RTS techniques [5, 8, 27, 29] have shown that they can be cost e ective. One cost bene ts tradeo among RTS techniques involves safety and eciency. Safe RTS techniques guarantee that, under certain conditions, test cases not selected could not have exposed faults in ....

....studies of some RTS techniques [5, 8, 27, 29] have shown that they can be cost e ective. One cost bene ts tradeo among RTS techniques involves safety and eciency. Safe RTS techniques guarantee that, under certain conditions, test cases not selected could not have exposed faults in P [25]. Achieving safety, however, may require inclusion of a larger number of test cases than can be run in available testing time. Non safe RTS techniques sacri ce safety for eciency, selecting test cases that, in some sense, are more useful than those excluded. 2.1.3 Test Suite Reduction As P ....

G. Rothermel and M. Harrold. Analyzing regression test selection techniques. IEEE Trans. Softw. Eng., 22(8):529-551, Aug. 1996.

....engineers may simply reuse all non obsolete test cases in T to test P # ; this is known as the retest all technique [22] and represents typical current practice [27] The retest all technique can be unnecessarily expensive. Regression test selection (RTS) techniques [2, 4, 11, 18, 23, 33] [32] provides a survey) attempt to reduce this cost by using information about P , P # , Test cases in T that no longer apply to P # are obsolete, and must be reformulated or discarded [22] and T to select a subset of T for use in testing P # . Empirical studies [3, 4, 12, 34, 35] have shown that ....

....[3, 4, 12, 34, 35] have shown that at least some of these techniques can be cost e#ective. One cost benefits tradeo# among RTS techniques involves safety and e#ciency. Safe RTS techniques [2, 4, 33] guarantee that, under certain conditions, excluded test cases could not have exposed faults in P # [32]. Achieving safety, however, may require inclusion of a larger number of test cases than can be run in available testing time. Non safe RTS techniques, which include techniques that attempt to minimize test cases for coverage [11, 15, 18, 23] sacrifice safety for e#ciency, selecting enough test ....

G. Rothermel and M. J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, Aug. 1996.

....engineers may simply reuse all non obsolete test cases in T to test P ; this is known as the retest all technique [22] and represents typical current practice [26] The retest all technique can be unnecessarily expensive. Regression test selection (RTS) techniques [2, 4, 11, 18, 23, 31] [30] provides a survey) attempt to reduce this cost by using information about P , P , and T to select a subset of T for use in testing P . Empirical studies [3, 4, 12, 32, 33] have shown that at least some of these techniques can be cost e ective. Test cases in T that no longer apply to P ....

....that no longer apply to P are obsolete, and must be reformulated or discarded [22] One cost bene ts tradeo among RTS techniques involves safety and eciency. Safe RTS techniques [2, 4, 31] guarantee that, under certain conditions, test cases not selected could not have exposed faults in P [30]. Achieving safety, however, may require inclusion of a larger number of test cases than can be run in available testing time. Non safe RTS techniques, which include techniques that attempt to minimize test cases for coverage [11, 15, 18, 23] sacri ce safety for eciency, selecting test cases ....

G. Rothermel and M. J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529-551, Aug. 1996.

.... of test suite reduction is to reduce the costs associated with regression testing: the retesting of software following modifications [10] In this context, it is worth di#erentiating test suite reduction from another approach used to reduce regression testing costs: regression test selection [14]. Regression test selection techniques take a program P , modified version P # of P , and test suite T for P , and attempt to select a subset of T for use in testing P # . The selected test cases are re used to test P # , but the non selected test cases are retained for use on future versions. ....

G. Rothermel and M. J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, August 1996.

....can be expensive: rerunning all test cases may require an unacceptable amount of time or human effort. Regression test selection (selection) techniques [4, 12, 17] use information about P , P , and T to select a subset of T with which to test P . For a survey of selection techniques, see [16]. As P evolves, new test cases may be added to T to validate new functionality. Over time, T grows, and its test cases become redundant in terms of code or functionality exercised. Test suite reduction (reduction) techniques [3, 9, 13] address this problem by using information Test cases in T ....

G. Rothermel and M. Harrold. Analyzing regression test selection techniques. IEEE Trans. Softw. Eng., 22(8):529--551, Aug. 1996.

....ordering on test cases the characteristic essential to the definition of prioritization. Rather, the approach selects a subset of a test suite, using history information to determine which test cases should be selected, and is more accurately described as a regression test selection technique [17]. 5 Avritzer and Weyuker [1] present techniques for generating test cases that apply to software that can be modeled by Markov chains, provided that operational profile data is available. Although the authors do not use the term prioritization , their techniques generate test cases in an order ....

G. Rothermel and M. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, Aug. 1996.

....methodology has not taken advantage of previously developed test cases, but as the preceding scenarios suggest, there are many reasons for doing so. Further, although test re use has been frequently addressed for the imperative paradigm, particularly in the context of regression testing, e.g. [8, 16, 19, 23, 29]) it has not yet been considered for the spreadsheet language paradigm. We have therefore been investigating ways to add support for test re use into our spreadsheet testing methodology. We have developed algorithms for saving test cases in spreadsheet programs that operate in concert with the ....

....multiple smaller changes in succession; these can be handled by incrementally processing each of these smaller changes. Applying ProcessMod incrementally following each modification avoids problems that can occur when multiple modifications, which may interfere, are processed simultaneously [23]. ProcessMod relies on the fact that when a formula for a cell is edited, we already possess, attached to that cell, a list of all test cases that exercise that formula; this list includes all test cases that could be affected by the edit. The outer loop of the algorithm processes these test ....

[Article contains additional citation context not shown here]

G. Rothermel and M. J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8), Aug. 1996.

....and modified program version, and selects test cases that are appropriate for that version without removing them from the test suite. The problems of regression test selection and test suite reduction are thus related but distinct. For further discussion of regression test selection see Reference [16]. Recent studies by Wong, Horgan, London, and Mathur [19, 20] 2 and Wong, Horgan, Mathur, and Pasquini [21] however, directly examine the costs and benefits of test suite reduction. We refer to these studies col lectively as the WHLMP studies, and individually as the WHLM and WHMP ....

G. Rothermel and M. J. Marrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529-551, August 1996.

....of a test suite. Leung and White [28] and Rosenblum and Weyuker [44] present techniques to assess regression testability. These techniques permir estimation, prior to regression test selection, of the Rothermel and Harrold present comprehensive comparison of regression test selection techniques [46]. number of test cases that will be selected by a method. Other techniques, such as that developed by Stafford, Richardson, and Wolf evaluate the difficulty of regression testing on precode artifacts [51] Because most software development involves the application of modifications to existing ....

G. Rothermel and M. J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Soft- ware Engineering, 22(8), August 1996.

....technique can be expensive: rerunning all test cases may require an unacceptable amount of time or human effort. Regression test selection (RTS) techniques [5, 17, 25] use information about P , P 0 , and T to select a subset of T with which to test P 0 . For a survey of RTS techniques, see [24]. Empirical studies of some RTS techniques [5, 8, 26, 28] have shown that they can be cost effective. One cost benefits tradeoff among RTS techniques involves safety and efficiency. Safe RTS techniques guarantee that, under certain conditions, test cases not selected could not have exposed ....

....studies of some RTS techniques [5, 8, 26, 28] have shown that they can be cost effective. One cost benefits tradeoff among RTS techniques involves safety and efficiency. Safe RTS techniques guarantee that, under certain conditions, test cases not selected could not have exposed faults in P 0 [24]. Achieving safety, however, may require inclusion of a larger number of test cases than can be run in available testing time. Non safe RTS techniques sacrifice safety for efficiency, selecting test cases that, in some sense, are more useful than those excluded. 2.1.3 Test Suite Reduction As P ....

G. Rothermel and M. Harrold. Analyzing regression test selection techniques. IEEE Trans. Softw. Eng., 22(8):529--551, Aug. 1996.

....are reluctant, however, to omit from a test suite any test case that might expose a fault in the modified software. A safe regression test selection technique is one that, under certain assumptions, selects every test case from the original test suite that can expose faults in the modified program [32]. To date, several safe regressiontest selection techniques have been developed [3, 8, 29, 31, 35] These techniques use some representation of the original and modified versions of the software to select a subset of the test suite to use in regression testing. Empirical evaluation of these ....

Gregg Rothermel and Mary Jean Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, Aug. 1996.

.... the algorithms presented in this paper; moreover, in all empirical data gathered to date on the use of the approach in practice, the bit vector approach has proven as precise as an approach involving more extensive trace encoding [47] 4 For a comprehensive list and review of the research, see [46]. 6 3. If necessary, create T 00 , a set of new functional or structural test cases for P 0 . 4. Test P 0 with T 00 , establishing P 0 s correctness with respect to T 00 . 5. Create T 000 , a new test suite and test history for P 0 , from T , T 0 , and T 00 . In performing ....

....test selection problem at all three of these levels of testing: application program testing, class testing, and derived class testing. 3 Selecting regression tests for modified application programs Reference [47] presented a technique, based on theoretical foundations presented in Reference [46], for selecting regression tests for procedural software. That technique includes both intraprocedural and interprocedural algorithms. Those algorithms, however, operate on individual CFGs. In this paper, the technique of [47] is modified to provide an algorithm that functions on ICFGs and ....

[Article contains additional citation context not shown here]

G. Rothermel and M.J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, August 1996.

....code running the entire test suite requires seven weeks. On the other hand, omitting test cases from the test suite can potentially result in the exclusion of a fault revealing test case. If the testing 1 requirements do not forbid this risk, a regression test selection (RTS) technique (e.g. [2, 5, 6, 8, 11, 13, 15, 18, 19, 25, 29, 31, 32]) can be employed; such techniques select a subset of the test suite using heuristics or analytic approaches. Different RTS techniques satisfy different demands. The simplest RTS techniques select test cases randomly, whereas more complex techniques typically base their selection on code analysis ....

....a general framework for safe RTS a framework that specifies what safe RTS means with respect to these different types of programs. So far, little has been done to establish a set of requirements to govern, or a model with which to evaluate, safe RTS techniques in general. Rothermel and Harrold [25] provide a framework for comparing and analyzing regression test selection techniques [25] but that framework does not specifically address the foundations of safe RTS. Ball [5] addresses the theoretical foundations of control flow graph based safe RTS techniques such as DejaVu and shows that the ....

[Article contains additional citation context not shown here]

G. Rothermel and M.J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, August 1996.

.... [30] Similarly, although there are safe regression test selection techniques (e.g. 3, 7, 29, 34] that can ensure that the selected subset of a test suite has the same fault detection capabilities as the original test suite, the conditions under which safety can be achieved do not always hold [28, 29]. Test case prioritization techniques [31, 36] provide another method for assisting with regression testing. 1 These techniques let testers order their test cases so that those test cases with the highest priority, according to some criterion, are executed earlier in the regression testing ....

G. Rothermel and M. J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, August 1996.

....test selection problem: the problem of selecting a subset T 0 of T with which to test P 0 . This problem includes the subproblem of identifying tests in T that are obsolete for P 0 . Test t is obsolete for P 0 if t speci es an 3 For a comprehensive list and review of the research, see [46]. 6 input to P 0 that, according to S 0 , is invalid for P 0 , or t speci es an invalid input output relation for P 0 . Step 3 addresses the coverage identi cation problem: the problem of identifying portions of P 0 or S 0 that require additional testing. Steps 2 and 4 address the ....

....selection problem at all three of these levels of testing: applications program testing, class testing, and derived class testing. 3 Selecting regression tests for modi ed applications programs In Reference [47] we presented a technique, based on theoretical foundations presented in Reference [46], for selecting regression tests for procedural software. That technique includes both intraprocedural and interprocedural algorithms. Those algorithms, however, operate on individual CFGs. We here modify that technique 7 to provide an algorithm that functions on ICFGs and supports regression ....

[Article contains additional citation context not shown here]

G. Rothermel and M.J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529-551, August 1996.

....4, 5, 6, 8, 11, 14, 22, 24, 26] address this problem. In this paper we are primarily interested in safe RTS techniques (e.g. 3, 6, 14, 22, 24] which by definition eliminate only test cases that are provably not able to reveal faults. This notion of safety is defined formally and in detail in [20, 21]; we summarize relevant points of that discussion here. A test case t detects a fault in P 0 if it causes P 0 to fail: in that case we say t is fault revealing for P 0 . A program P fails for t if, when P is tested with t, P produces an output that is incorrect according to S. There is no ....

....may miss important faults that it is expressly designed to be able to expose if, for example, lack of control causes its test cases to behave in unintended ways and no longer exercise the code or features they are meant to exercise. Further ramifications of this assumption are discussed in [20, 21]. The techniques we examine in this paper techniques implemented as DejaVu and TestTube are both safe and depend for their safety on the set of assumptions just described. Both techniques attempt to identify, though at different levels, the test cases in T that are modification traversing ....

[Article contains additional citation context not shown here]

G. Rothermel and M.J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, August 1996.

....OPS and ETS are of interest in this context because of their relationship to regression testing. One important regression testing activity is the selection of a subset of the test suite that was originally used to test a program, for use in testing a modified version of that program; Reference [13] provides details. In brief, given a program P , a test suite T for P , and a modified program version P 0 , testers want to identify the test cases in T that reveal regression faults in P 0 . For test cases whose specified behavior has not changed, these fault revealing test cases are ....

G. Rothermel and M.J. Harrold. Analyzing regression test selection techniques. IEEE Trans. on Softw. Eng., 22(8):529--551, August 1996.

....of Computer Science, Oregon State University. 4 AT T Labs Research. 5 A variety of selective regression testing techniques have been proposed (e.g. 1, 3, 4, 6, 7, 8, 9, 10, 12, 13, 15, 16, 18, 21, 26, 27, 28, 29, 30] For an overview and analytical comparison of these techniques, see [25]. 1 regression testing algorithm, implemented as a tool called TestTube [8] also show that such methods are not always cost effective [23] When selective regression testing is not cost effective, the resources spent performing the test case selection are wasted. Thus, Rosenblum and Weyuker ....

....Harrold divide regression testing into two phases for the purpose of cost analysis. During the preliminary phase, changes are made to the software, and the new version of the software is built. During the critical phase, the new version of the software is tested prior to its release to customers [25]. 19 Test Suites T 1 T 2 T 3 T 4 T 5 T 6 T 7 T 8 Gamma999 T 1000 DejaVu j 54.8 61.6 53.0 54.0 58.0 55.1 56.0 : 54.8 S DejaVu i;j Version 1 58.3 81.8 62.5 60.0 84.6 62.5 72.7 : 50.0 Version 2 8.3 9.1 12.5 10.0 7.7 12.5 9.1 : 7.1 Version 3 16.7 18.2 25.0 10.0 23.1 12.5 18.2 : 21.4 ....

G. Rothermel and M.J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, August 1996.

....modified program version, and selects test cases that are appropriate for that version without removing them from the test suite. The problems of regression test selection and test suite minimization are thus related but distinct. For further discussion of regression test selection see Reference [12]. in terms of averages over groups of test cases that achieved similar coverage: 89 test suites belonged to groups in which average test suite size ranged from 12 to 27 test cases, and 933 test suites belonged to groups in which average test suite size ranged from 1 to 7 test cases. The ....

G. Rothermel and M. Harrold. Analyzing regression test selection techniques. IEEE Trans. on Softw. Eng., 22(8):529-- 551, Aug. 1996.

....OPS and ETS are of interest in this context because of their relationship to regression testing. One important regression testing activity is the selection of a subset of the test suite that was originally used to test a program, for use in testing a modified version of that program; Reference [13] provides details. In brief, given a program P , a test suite T for P , and a modified program version P # , testers want to identify the test cases in T that reveal regression faults in P # . For test cases whose specified behavior has not changed, these fault revealing test cases are exactly ....

G. Rothermel and M.J. Harrold. Analyzing regression test selection techniques. IEEE Trans. on Softw. Eng., 22(8):529--551, August 1996.

.... [30] Similarly, although there are safe regression test selection techniques (e.g. 3, 7, 29, 34] that can ensure that the selected subset of a test suite has the same fault detection capabilities as the original test suite, the conditions under which safety can be achieved do not always hold [28, 29]. Test case prioritization techniques [31, 36] provide another method for assisting with regression testing. 1 These techniques let testers order their test cases so that those test cases with the highest priority, according to some criterion, are executed earlier in the regression testing ....

G. Rothermel and M. J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, August 1996.

....which executes this pair, is associated with that requirement. If test selection determines that this definition use pair is affected by a change in P , then t1 is added to T 0 . New code induces definition use pairs in P 0 that are not present in P . Because these definition use pairs 6 See [29] for a thorough discussion of these techniques. 7 A definition use pair is a pair of statements (S1; S2) such that S1 defines some variable v, S2 uses v, and there is a path in the program from S1 to S2 along which v is not redefined. 5 do not exist for P , there are no tests in T associated ....

....pair in P 0 , it was not selected. Thus, this technique is unsafe. To date, there have been a number of empirical studies that evaluate these regression test selection techniques. Using DejaVu, we investigated the costs and benefits of using our regression test selection algorithm [29, 26]. We used DejaVu to select tests for a variety of 100 500 line programs, for which savings averaged 45 , and for a larger (50,000 line) software system, for which savings averaged 95 . Our studies show that the cost effectiveness of test selection can vary widely based on a number of factors: the ....

[Article contains additional citation context not shown here]

G. Rothermel and M.J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8), August 1996.

.... [26] Similarly, although there are safe regression test selection techniques (e.g. 2, 5, 25, 30] that ensure that the selected subset of a test suite has the same fault detection capabilities as the original test suite, the conditions under which safety can be achieved do not always hold [24, 25]. Test case prioritization techniques [27, 34] provide another method for assisting with regression testing. Test case prioritization techniques attempt to schedule test cases for regression testing in an order that increases their effectiveness in meeting some performance goal. These techniques ....

G. Rothermel and M.J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, August 1996.

No context found.

G. Rothermel and M. Harrold. Analyzing regression test selection techniques. IEEE Trans. on Softw. Eng., 22(8):529--551, Aug. 1996.

No context found.

G. Rothermel and M. J. Harrold. Analyzing regression test selection techniques. IEEE TSE, 22(8):529--551, Aug. 1996.

No context found.

G. Rothermel and M. J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, Aug. 1996.

No context found.

G. Rothermel and M. J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, 1996.

No context found.

G. Rothermel and M. J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, 1996.

No context found.

G. Rothermel and M. J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, 1996.

No context found.

G. Rothermel and M. J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, Aug. 1996.

No context found.

G. Rothermel and M. J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529--551, 1996.

No context found.

G. Rothermel, M. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8). August 1996.

No context found.

G. Rothermel and M. J. Harrold. Analyzing regression test selection techniques. In Proceedings. Communications of the ACM, volume 41(5), pages 81--86, 1998.

First 50 documents  Next 50

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC