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. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Benji Cooper

dblp:225/7834 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 2018
—ORCID · none

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

Security and privacy · 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 · 62% Empirical software engineering · 38%

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

TopicWeightPapersLastEvidence papers
Software testing
fuzzing
0.312018
Evaluating Fuzz Testing · CCS 2018
Empirical software engineering › benchmarking
benchmarking methodology
0.112018
Evaluating Fuzz Testing · CCS 2018
Empirical software engineering › software engineering research methodology
empirical study
0.112018
Evaluating Fuzz Testing · CCS 2018

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

survey · 0.3experimental evaluation · 0.3
YearPublicationVenuePosition
2018 Evaluating Fuzz Testing
abstract
Fuzz testing has enjoyed great success at discovering security critical bugs in real software. Recently, researchers have devoted significant effort to devising new fuzzing techniques, strategies, and algorithms. Such new ideas are primarily evaluated experimentally so an important question is: What experimental setup is needed to produce trustworthy results? We surveyed the recent research literature and assessed the experimental evaluations carried out by 32 fuzzing papers. We found problems in every evaluation we considered. We then performed our own extensive experimental evaluation using an existing fuzzer. Our results showed that the general problems we found in existing experimental evaluations can indeed translate to actual wrong or misleading assessments. We conclude with some guidelines that we hope will help improve experimental evaluations of fuzz testing algorithms, making reported results more robust.
George Klees, Andrew Ruef, Benji Cooper, Shiyi Wei, Michael Hicks 0001
CCS3