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

Fabio Di Lauro

dblp:292/2100 · DBLP profile ↗
← Back
5ranked-venue papers
4as first author
5since 2021 · last 2025
0000-0001-6982-9851ORCID · corroborated

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

Software engineering, systems software and programming languages · 5 · 4 first-author · 5 since 2021Databases, data management, data science and information retrieval · 2 · 2 first-author · 2 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 · 91% Software maintenance and evolution · 9%

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

TopicWeightPapersLastEvidence papers
Software testing › test execution
parallel testing
0.912025
Parallelization in System-Level Testing: Novel Approaches to Manage Test Suite Dependencies · IEEE Trans. Software Eng. 2025
Software testing
system testing
0.912025
Parallelization in System-Level Testing: Novel Approaches to Manage Test Suite Dependencies · IEEE Trans. Software Eng. 2025
Software testing
test dependency detection
0.912025
Parallelization in System-Level Testing: Novel Approaches to Manage Test Suite Dependencies · IEEE Trans. Software Eng. 2025
Software maintenance and evolution › release engineering
continuous integration
0.312025
Parallelization in System-Level Testing: Novel Approaches to Manage Test Suite Dependencies · IEEE Trans. Software Eng. 2025

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

optimistic scheduling · 0.9dependency detection algorithms · 0.9
YearPublicationVenuePosition
2025 Parallelization in System-Level Testing: Novel Approaches to Manage Test Suite Dependencies
abstract
System-level testing is fundamental to ensure the reliability of software systems. However, the execution time for system tests can be quite long, sometimes prohibitively long, especially in a regimen of continuous integration and deployment. One way to speed things up is to run the tests in parallel, provided that the execution schedule respects any dependency between tests. We present two novel approaches to detect dependencies in system-level tests, namely PFAST and MEM-FAST, which are highly parallelizable and optimistically run test schedules to exclude many dependencies when there are no failures. We evaluated our approaches both asymptotically and practically, on six Web applications and their system-level test suites, as well as on MySQL system-level tests. Our results show that, in general, PFAST is significantly faster than the state-of-the-art PRADET dependency detection algorithm, while producing parallelizable schedules that achieve a significant reduction in the overall test suite execution time.
Pasquale Polverino, Fabio Di Lauro, Matteo Biagiola, Paolo Tonella, Antonio Carzaniga
IEEE Trans. Software Eng.2
2024 GitHub-Sourced Web API Evolution: A Large-Scale OpenAPI Dataset
Fabio Di Lauro
ICWE1
2022 To Deprecate or to Simply Drop Operations? An Empirical Study on the Evolution of a Large OpenAPI Collection
Fabio Di Lauro, Souhaila Serbout, Cesare Pautasso
ECSA1
2022 A Large-scale Empirical Assessment of Web API Size Evolution
abstract
Like any other type of software, also Web Application Programming Interfaces (APIs) evolve over time. In the case of widely used API, introducing changes is never a trivial task, because of the risk of breaking thousands of clients relying on the API. In this paper we conduct an empirical study over a large collection of OpenAPI descriptions obtained by mining open source repositories. We measure the speed at which Web APIs change and how changes affect their size, simply defined as the number of operations. The dataset of API descriptions was collected over a period of one year and includes APIs with histories spanning across up to 7 years of commits. The main finding is that APIs tend to grow, although some do reduce their size, as shown in the case study examples included in the appendix.
Fabio Di Lauro, Souhaila Serbout, Cesare Pautasso
J. Web Eng.1
2021 Towards Large-Scale Empirical Assessment of Web APIs Evolution
Fabio Di Lauro, Souhaila Serbout, Cesare Pautasso
ICWE1