Demo Data from EDBT 2026 / reviewers in the wild / expert
Ben Lambeth
dblp:190/1133
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2016
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1
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 · 50% Debugging and program repair · 50% |
Topics — the 2 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Debugging and program repair
fault localization |
0.2 | 1 | 2016 | NonDex: a tool for detecting and debugging wrong assumptions on Java API specifications · SIGSOFT FSE 2016 |
Software testing
test execution |
0.2 | 1 | 2016 | NonDex: a tool for detecting and debugging wrong assumptions on Java API specifications · SIGSOFT FSE 2016 |
Methods — techniques the papers use, named apart from their topics
test execution · 0.2random exploration · 0.2
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2016 | NonDex: a tool for detecting and debugging wrong assumptions on Java API specificationsabstractWe present NonDex, a tool for detecting and debugging wrong assumptions on Java APIs. Some APIs have underdetermined specifications to allow implementations to achieve different goals, e.g., to optimize performance. When clients of such APIs assume stronger-than-specified guarantees, the resulting client code can fail. For example, HashSet’s iteration order is underdetermined, and code assuming some implementation-specific iteration order can fail. NonDex helps to proactively detect and debug such wrong assumptions. NonDex performs detection by randomly exploring different behaviors of underdetermined APIs during test execution. When a test fails during exploration, NonDex searches for the invocation instance of the API that caused the failure. NonDex is open source, well-integrated with Maven, and also runs from the command line. During our experiments with the NonDex Maven plugin, we detected 21 new bugs in eight Java projects from GitHub, and, using the debugging feature of NonDex, we identified the underlying wrong assumptions for these 21 new bugs and 54 previously detected bugs. We opened 13 pull requests; developers already accepted 12, and one project changed the continuous-integration configuration to run NonDex on every push. The demo video is at: https://youtu.be/h3a9ONkC59c Alex Gyori, Ben Lambeth, August Shi, Owolabi Legunsen, Darko Marinov |
SIGSOFT FSE | 2 |