On the Retesting Methodology and Reusing Test Cases for Software Maintenance


The Transactions of the Korea Information Processing Society (1994 ~ 2000), Vol. 2, No. 1, pp. 45-54, Jan. 1995
10.3745/KIPSTE.1995.2.1.45,   PDF Download:

Abstract

Retest arises when attempting to validate code modifications. This paper proposes a retest methodology which explicitly defines the amount of retesting to be performed for any given code change. In order to minimize the objective function, we use the set/use matrix through analysis of data dependence as well as the connectivity, reachability, and test case/reference matrix through program control flow analysis. The value of objective function will give the minimum number of test cases necessary to assure the proposed methodology, we develope the retesting tool for generating minimum test cases based on the function.


Statistics
Show / Hide Statistics

Statistics (Cumulative Counts from September 1st, 2017)
Multiple requests among the same browser session are counted as one view.
If you mouse over a chart, the values of data points will be shown.


Cite this article
[IEEE Style]
H. S. Myung and J. Y. Taek, "On the Retesting Methodology and Reusing Test Cases for Software Maintenance," The Transactions of the Korea Information Processing Society (1994 ~ 2000), vol. 2, no. 1, pp. 45-54, 1995. DOI: 10.3745/KIPSTE.1995.2.1.45.

[ACM Style]
Hwang Sun Myung and Jin Yong Taek. 1995. On the Retesting Methodology and Reusing Test Cases for Software Maintenance. The Transactions of the Korea Information Processing Society (1994 ~ 2000), 2, 1, (1995), 45-54. DOI: 10.3745/KIPSTE.1995.2.1.45.