Demo Data from EDBT 2026 / reviewers in the wild / expert
Maaz Hafeez Ur Rehman
dblp:299/8738
· DBLP profile ↗
1ranked-venue papers
1as first author
1since 2021 · last 2021
—ORCID · none
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 · 100% |
Topics — the 2 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Software testing
flaky test |
0.5 | 1 | 2021 | Quantifying no-fault-found test failures to prioritize inspection of flaky tests at Ericsson · ESEC/SIGSOFT FSE 2021 |
Software testing › fault analysis
test failure analysis |
0.5 | 1 | 2021 | Quantifying no-fault-found test failures to prioritize inspection of flaky tests at Ericsson · ESEC/SIGSOFT FSE 2021 |
Methods — techniques the papers use, named apart from their topics
empirical analysis · 0.5case study · 0.5
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2021 | Quantifying no-fault-found test failures to prioritize inspection of flaky tests at EricssonabstractA test fails and despite an investigation by a developer there is no fault found (NFF). Large software systems are often released with known failing and flaky tests. In this work, we quantify how often a test fails and does not find a fault. We conduct a case study on 9.9 million test runs of 10k tests across four releases of a large project at Ericsson. Maaz Hafeez Ur Rehman, Peter C. Rigby |
ESEC/SIGSOFT FSE | 1 |