• Journal of Software Engineering Society
• /
• v.29 no.2
• /
• pp.1-6
• /
• 2020

Software product line development is a development paradigm that efficiently develops a product family by avoiding redundant development based on separation of the common part and the variable part of the product family. In software product line development, the source code that is used to produce a product family is called a product line code base, and when the product line code base is changed and the products of the product family are affected by the change, the activity of testing the affected products is called a product line regression testing. For product line regression testing, instead of conducting regression testing individually on each product of the product family, a more efficient regression testing would be possible if unnecessary testing that are irrelevant to the change can be avoided. This paper introduces SRTS, which is an automated method to efficiently perform software product line regression testing. SRTS divides the product line code base and test cases based on commonality and variability. Then SRTS identifies and selects the test cases affected by the change. Finally, it reduces unnecessary testing by rerunning only the selected test cases.

• Journal of Information Technology Services
• /
• v.14 no.2
• /
• pp.129-142
• /
• 2015

The purpose of this study is to suggest an effective regression testing method in order to minimize the scope of test resulting from the modification of software and to prevent mismatch of test case and test objects. As a way to improve the efficiency of regression testing which uses a change-centric testing technique, the method flow is analyzed and grasped through a static analysis based on source code in order to identify modified parts. After the order of priority is set according to the results of user action log-based dynamic analysis on identified regression testing objects, test effect can be raised by adjusting the order of priority using code complexity. Quality assurance coverage can be checked using the user action log suggested in this study, and the progress of test and whether or not each function has been verified can be checked, too. In addition, by minimizing test parts and adjusting the order of test, costs and time can be saved, making it possible to conduct regression testing effectively.

• Journal of Information Processing Systems
• /
• v.6 no.1
• /
• pp.21-32
• /
• 2010

Software maintenance is one of the major activities of the software development life cycle. Due to the time and cost constraint it is not possible to perform exhaustive regression testing. Thus, there is a need for a technique that selects and prioritizes the effective and important test cases so that the testing effort is reduced. In an analogous study we have proposed a new variable based algorithm that works on variables using the hybrid technique. However, in the real world the programs consist of multiple modules. Hence, in this work we propose a regression testing algorithm that works on interprocedural programs. In order to validate and analyze this technique we have used various programs. The result shows that the performance and accuracy of this technique is very high.

• Journal of Information Processing Systems
• /
• v.6 no.2
• /
• pp.235-252
• /
• 2010

Regression testing is a very costly process performed primarily as a software maintenance activity. It is the process of retesting the modified parts of the software and ensuring that no new errors have been introduced into previously tested source code due to these modifications. A regression test selection technique selects an appropriate number of test cases from a test suite that might expose a fault in the modified program. In this paper, we propose both a regression test selection and prioritization technique. We implemented our regression test selection technique and demonstrated in two case studies that our technique is effective regarding selecting and prioritizing test cases. The results show that our technique may significantly reduce the number of test cases and thus the cost and resources for performing regression testing on modified software.

• Communications for Statistical Applications and Methods
• /
• v.11 no.3
• /
• pp.475-484
• /
• 2004

This paper consider the testing problem of grouped heteroscedasticity in the linear regression model. We provide the Lagrange Multiplier(LM), Wald, Likelihood Ratio (LR) test statistis for testing of grouped heteroscedasticity. Monte Carlo experiments are conducted to study the performance of these tests.

• Journal of applied mathematics & informatics
• /
• v.26 no.3_4
• /
• pp.679-688
• /
• 2008

In multivariate regression analysis there exist many influence measures on the regression estimates. However it seems to be few of influence diagnostics on test statistics in hypothesis testing. Case-deletion approach is fundamental for investigating influence of observations on estimates or statistics. Tang and Fung (1997) derived single case-deletion of the Wilks' ratio, Lawley-Hotelling trace, Pillai's trace for testing a general linear hypothesis of the regression coefficients in multivariate regression. In this paper we derived more extended form of those measures to deal with joint influence among observations. A numerical example is given to illustrate the effect of joint influence on the test statistics.

• Journal of the Korea Institute of Information Security & Cryptology
• /
• v.31 no.5
• /
• pp.911-917
• /
• 2021

As software gets an increasing amount of patches, lots of software bugs are increasingly caused by such software patches, collectively known as regression bugs. To proactively detect the regressions bugs, both industry and academia are actively searching for a way to augment fuzz testing, one of the most popular automatic bug detection techniques. In this paper, we investigate the status quo of the studies on augmenting fuzz testing for regression bug detection and, based on the limitations of current proposals, provide an outlook of the relevant research.

• Journal of Digital Convergence
• /
• v.11 no.3
• /
• pp.293-298
• /
• 2013

We consider about software quality nowadays. The company considers about software quality more and more compare to software development. We analyze the software testing data in this paper. We find the software effect according to the number of testing, the number of testing date, the number of fault according to characteristics. Also, we analyze the result by regression. Also, we propose the testing effect by sex.

• Journal of the Korea Society of Computer and Information
• /
• v.26 no.8
• /
• pp.157-164
• /
• 2021

Regression analysis is a well-known statistical technique useful to explain the relationship between response variable and predictor variables. In particular, Researchers are interested in comparing the regression coefficients(intercepts and slopes) of the models in two independent populations. The Chow test, proposed by Gregory Chow, is one of the most commonly used methods for comparing regression models and for testing the presence of a structural break in linear models. In this study, we propose the use of permutation method and compare it with Chow test analysis for testing the equality of two independent linear regression models. Then simulation study is conducted to examine the powers of permutation test and Chow test.

• Journal of KIISE:Software and Applications
• /
• v.27 no.4
• /
• pp.370-383
• /
• 2000

This paper describes a new technique known as specification-based regression testing that is used for the revalidation of concurrent programs after changes are made to specifications. This type of regression testing requires sequencing constraint that specify precedence relations on the synchronization events. In order to extract sequencing constraint automatically, we use Message Sequence Charts(MSCs) that are considered partial and nondeterministic specifications. We show how to identify which sequencing constraint is affected by the modifications made to a specification rather than creating new sequencing constraint from scratch to reduce the cost of regression testing. We also describe how to determine that each affected sequencing constraint is satisfied by a program being tested.