Demo Data from VLDB 2026 / reviewers in the wild / expert
Maryam Masoudian
dblp:383/7695
· DBLP profile ↗
1ranked-venue papers
1as first author
1since 2021 · last 2024
0000-0003-1111-2908ORCID · reported
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 1 first-author · 1 since 2021
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
1 paper |
Software testing · 36% Debugging and program repair · 32% Program analysis · 16% |
Topics — the 7 heaviest of 7, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Debugging and program repair › bug reproduction
crash reproduction |
0.8 | 1 | 2024 | Mole: Efficient Crash Reproduction in Android Applications With Enforcing Necessary UI Events · IEEE Trans. Software Eng. 2024 |
Software testing › fuzzing
directed fuzzing |
0.8 | 1 | 2024 | Mole: Efficient Crash Reproduction in Android Applications With Enforcing Necessary UI Events · IEEE Trans. Software Eng. 2024 |
Debugging and program repair
fault localization |
0.8 | 1 | 2024 | Mole: Efficient Crash Reproduction in Android Applications With Enforcing Necessary UI Events · IEEE Trans. Software Eng. 2024 |
Software testing
fuzzing |
0.8 | 1 | 2024 | Mole: Efficient Crash Reproduction in Android Applications With Enforcing Necessary UI Events · IEEE Trans. Software Eng. 2024 |
Program verification › model checking › state space exploration
reachability analysis |
0.8 | 1 | 2024 | Mole: Efficient Crash Reproduction in Android Applications With Enforcing Necessary UI Events · IEEE Trans. Software Eng. 2024 |
Program analysis
static analysis |
0.8 | 1 | 2024 | Mole: Efficient Crash Reproduction in Android Applications With Enforcing Necessary UI Events · IEEE Trans. Software Eng. 2024 |
Software testing › fuzzing
GUI fuzzing |
0.2 | 1 | 2024 | Mole: Efficient Crash Reproduction in Android Applications With Enforcing Necessary UI Events · IEEE Trans. Software Eng. 2024 |
Methods — techniques the papers use, named apart from their topics
static UI modeling · 0.8instrumentation · 0.8
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2024 | Mole: Efficient Crash Reproduction in Android Applications With Enforcing Necessary UI EventsabstractTo improve the quality of Android apps, developers use automated debugging and testing solutions to determine whether the previously found crashes are reproducible. However, existing GUI fuzzing solutions for Android apps struggle to reproduce crashes efficiently based solely on a crash stack trace. This trace provides the location in the app where the crash occurs. GUI fuzzing solutions currently in use rely on heuristics to generate UI events. Unfortunately, these events often do not align with the investigation of an app's UI event space to reach a specific location of code. Hence, they generate numerous events unrelated to the crash, leading to an event explosion. To address this issue, a precise static UI model of widgets and screens can greatly enhance the efficiency of a fuzzing tool in its search. Building such a model requires considering all possible combinations of event sequences on widgets since the execution order of events is not statically determined. However, this approach presents scalability challenges in complex apps with several widgets. In this paper, we propose a directed-based fuzzing solution to reduce an app's event domain to the necessary ones to trigger a crash. Our insight is that the dependencies between widgets in their visual presentation and attribute states provide valuable information in precisely identifying events that trigger a crash. We propose an attribute-sensitive reachability analysis (ASRA) to track dependent widgets in reachable paths to the crash point and distinguish between events in terms of their relevancy to be generated in the crash reproduction process. With instrumentation, we inject code to prune irrelevant events, reducing the event domain to search at run time. We used four famous fuzzing tools, Monkey, Ape, Stoat, and FastBot2, to assess the impact of our solution in decreasing the crash reproduction time and increasing the possibility of reproducing a crash. Our results show that the success ratio of reproducing a crash has increased forone-fourthof crashes. In addition, the average reproduction time of a crash becomes at least 2x faster. Wilcoxon Mann-Whitney test shows this enhancement is significant when our tool is used compared to baseline and insensitive reachability analysis. Maryam Masoudian, Heqing Huang 0002, Morteza Amini, Charles Zhang 0001 |
IEEE Trans. Software Eng. | 1 |