Demo Data from EDBT 2026 / reviewers in the wild / expert
Md Mazba Ur Rahman
dblp:367/2579
· DBLP profile ↗
1ranked-venue papers
0as first author
1since 2021 · last 2024
0000-0002-3106-4117ORCID · reported
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 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 |
Debugging and program repair · 40% Software testing · 40% Empirical software engineering · 20% |
Topics — the 5 heaviest of 5, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Debugging and program repair
automated program repair |
0.8 | 1 | 2024 | Poracle: Testing Patches under Preservation Conditions to Combat the Overfitting Problem of Program Repair · ACM Trans. Softw. Eng. Methodol. 2024 |
Software testing › fuzzing
differential fuzzing |
0.8 | 1 | 2024 | Poracle: Testing Patches under Preservation Conditions to Combat the Overfitting Problem of Program Repair · ACM Trans. Softw. Eng. Methodol. 2024 |
Software testing
fuzzing |
0.8 | 1 | 2024 | Poracle: Testing Patches under Preservation Conditions to Combat the Overfitting Problem of Program Repair · ACM Trans. Softw. Eng. Methodol. 2024 |
Debugging and program repair › automated program repair › patch correctness assessment
overfitting patch detection |
0.8 | 1 | 2024 | Poracle: Testing Patches under Preservation Conditions to Combat the Overfitting Problem of Program Repair · ACM Trans. Softw. Eng. Methodol. 2024 |
Empirical software engineering › AI for software engineering › machine learning for software engineering
patch classification |
0.8 | 1 | 2024 | Poracle: Testing Patches under Preservation Conditions to Combat the Overfitting Problem of Program Repair · ACM Trans. Softw. Eng. Methodol. 2024 |
Methods — techniques the papers use, named apart from their topics
user study · 0.8differential fuzzing · 0.8
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2024 | Poracle: Testing Patches under Preservation Conditions to Combat the Overfitting Problem of Program RepairabstractTo date, the users of test-driven program repair tools suffer from the overfitting problem; a generated patch may pass all available tests without being correct. In the existing work, users are treated as merely passive consumers of the tests. However, what if they are willing to modify the test to better assess the patches obtained from a repair tool? In this work, we propose a novel semi-automatic patch-classification methodology named Poracle . Our key contributions are three-fold. First, we design a novel lightweight specification method that reuses the existing test. Specifically, the users extend the existing failing test with a preservation condition —the condition under which the patched and pre-patched versions should produce the same output. Second, we develop a fuzzer that performs differential fuzzing with a test containing a preservation condition. Once we find an input that satisfies a specified preservation condition but produces different outputs between the patched and pre-patched versions, we classify the patch as incorrect with high confidence. We show that our approach is more effective than the four state-of-the-art patch classification approaches. Last, we show through a user study that the users find our semi-automatic patch assessment method more effective and preferable than the manual assessment. Elkhan Ismayilzada, Md Mazba Ur Rahman, Dongsun Kim 0001, Jooyong Yi |
ACM Trans. Softw. Eng. Methodol. | 2 |