Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data.

Kai Yu 0013

dblp:197/1322-13 · DBLP profile ↗
← Back
7ranked-venue papers
5as first author
0since 2021 · last 2012
—ORCID · conflict

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 7 · 5 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
3 papers
Debugging and program repair · 70% Empirical software engineering · 23% Software testing · 7%

Topics — the 8 heaviest of 8, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Debugging and program repair
fault localization
0.432012
Practical isolation of failure-inducing changes for debugging regression faults · ASE 2012
An integrated bug processing framework · ICSE 2012
Improving failure-inducing changes identification using coverage analysis · ICSE 2012
Debugging and program repair
automated debugging
0.112012
Improving failure-inducing changes identification using coverage analysis · ICSE 2012
Empirical software engineering › mining software repositories
bug report analysis
0.112012
An integrated bug processing framework · ICSE 2012
Empirical software engineering › software fault analysis
bug study
0.112012
An integrated bug processing framework · ICSE 2012
Debugging and program repair › automated debugging
delta debugging
0.112012
Improving failure-inducing changes identification using coverage analysis · ICSE 2012
Debugging and program repair › regression debugging
failure-inducing change identification
0.112012
Improving failure-inducing changes identification using coverage analysis · ICSE 2012
Software testing › test coverage
coverage analysis
0.012012
Improving failure-inducing changes identification using coverage analysis · ICSE 2012
Software testing
regression testing
0.012012
Practical isolation of failure-inducing changes for debugging regression faults · ASE 2012

Methods — techniques the papers use, named apart from their topics

delta debugging · 0.3coverage analysis · 0.3fault localization · 0.1bug report analysis · 0.1
YearPublicationVenuePosition
2012 Improving failure-inducing changes identification using coverage analysis
abstract
Delta debugging has been proposed for failure-inducing changes identification. Despite promising results, there are two practical factors that thwart the application of delta debugging: large number of tests and misleading false positives. To address the issues, we present a combination of coverage analysis and delta debugging that automatically isolates failure-inducing changes. Evaluations on twelve real regressions in GNU software demonstrate both the speed gain and effectiveness improvements.
Kai Yu 0013
ICSE1
2012 An integrated bug processing framework
abstract
Software debugging starts with bug reports. Test engineers confirm bugs and determine the corresponding developers to fix them. However, the analysis of bug reports is time-consuming and manual inspection is difficult and tedious. To improve the efficiency of the whole process, we propose a bug processing framework that integrates bug report analysis and fault localization. An instance of the framework is implemented for regression faults. Preliminary results on a large open source application demonstrate both efficiency and effectiveness.
Mengxiang Lin, Kai Yu 0013
ICSE3
2012 When a GUI Regression Test Failed, What Should be Blamed?
abstract
Script-based automated regression testing is widely used in industry. In this work, we focus on failed tests in a real regression test project. The causes of 197 failed tests produced in automated testing are examined and categorized based on an analysis procedure presented. The result shows that incorrect scripts, oracle mismatches, test tool bugs and misconfigurations involved in testing contribute most to failures instead of product bugs. Detecting and fixing the false positives are laborious and time-consuming. Our empirical study demonstrates that the benefits of test automation are obliterated to some extent in practical settings. To improve the effectiveness of automated regression testing further, some issues should receive more attention.
Mengxiang Lin, Kai Yu 0013, Bing Shao
ICST3
2012 Towards Practical Debugging for Regression Faults
abstract
Regression faults are inevitably introduced in software development. Identifying and fixing regression faults can be tedious and time-consuming. The goal of my doctoral research is to provide an automated practical technique to effectively and efficiently locating failure-inducing changes. In this work, the research problem and related work is discussed first. Then, our approach, research questions, completed work and future work is presented. Finally, the expected contributions of my thesis are listed.
Kai Yu 0013, Mengxiang Lin
ICST1
2012 Practical isolation of failure-inducing changes for debugging regression faults
abstract
During software evolution, new released versions still contain many bugs. One common scenario is that end users encounter regression faults and submit them to bug tracking systems. Different from in-house regression testing, typically only one test input is available, which passes the old version and fails the modified new version. To address the issue, delta debugging has been proposed for failure-inducing changes identification between two versions. Despite promising results, there are two practical factors that thwart the application of delta debugging: a large number of tests and misleading false positives. In this work, we present a combination of coverage analysis and delta debugging that automatically isolates failure-inducing changes. Evaluations on twelve real regression faults in GNU software demonstrate both the speed gain and effectiveness improvements. Moreover, a case study on libPNG and TCPflow indicates that our technique is comparable to peer techniques in debugging regressions faults.
Kai Yu 0013, Mengxiang Lin
ASE1
2012 Towards automated debugging in software evolution: Evaluating delta debugging on real regression bugs from the developers' perspectives
Kai Yu 0013, Mengxiang Lin
J. Syst. Softw.1
2009 Program Sifting: Select Property-Related Functions for Language-Based Static Analysis
abstract
Recent studies have demonstrated that language-based static analysis is capable of finding hundreds of bugs in complex real systems. Such static analysis allows users to specify properties in a specification language on demand. Paths in control flow graphs are explored exhaustively against user-defined properties. To avoid the potential path explosion problem, many techniques have been used in practice such as summaries. In this paper, we investigate how to simplify programs under check utilizing user-specified properties. From our observations, most functions under check are irrelevant to given properties. Checking those functions is time consuming. A program sifting approach is proposed to select functions related to properties. Sifters are derived from user-specified properties automatically. Functions matched or affected by sifters are safely preserved while the others are safely removed. We implemented a tool SIFT and carried out some experiments. Results show that SIFT is capable of simplifying program under check remarkably with small cost. In our experiments, 85% functions in files are sifted out while 89% analysis time is saved on average.
Kai Yu 0013, Yin-li Chen, Mengxiang Lin
APSEC1