ICSE 2024
Fri 12 - Sun 21 April 2024 Lisbon, Portugal

Accepted Papers

AntiCopyPaster 2.0: Whitebox just-in-time code duplicates extraction
APICIA: An API Change Impact Analyzer for Android Apps
Boidae: Your Personal Mining Platform
Can My Microservice Tolerate an Unreliable Database? Resilience Testing with Fault Injection and Visualization
Media Attached
CATMA: Conformance Analysis Tool For Microservice Applications
Pre-print Media Attached
CodeGRITS: A Research Toolkit for Developer Behavior and Eye Tracking in IDE
Code Mapper: Mapping the Global Contributions of OSS
Daedalux: An Extensible Platform for Variability-Aware Model Checking
DronLomaly: Runtime Log-based Anomaly Detector for DJI Drones
Emulation Tool For Android Edge Devices
FaultFuzz: A Coverage Guided Fault Injection Tool for Distributed Systems
GitBug-Actions: Building Reproducible Bug-Fix Benchmarks with GitHub Actions
GitHubInclusifier: Finding and fixing non-inclusive language in GitHub Repositories
Pre-print Media Attached
JOG: Java JIT Peephole Optimizations and Tests from Patterns
MutaBot: A Mutation Testing Approach for Chatbots
DOI Pre-print Media Attached
(Neo4j)^ Browser: Visualizing Variable-Aware Analysis Results
nvshare: Practical GPU Sharing without Memory Size Constraints
OpenSBT: A Modular Framework for Search-based Testing of Automated Driving Systems
RAT: A Refactoring-Aware Tool for Tracking Code History
Refinery: Graph Solver as a Service
DOI Pre-print Media Attached
SAFE: Safety Analysis and Retraining of DNNs
Simulation-based Testing of Unmanned Aerial Vehicles with Aerialist
DOI Pre-print
SpotFlow: Tracking Method Calls and States at Runtime
TestSpark: IntelliJ IDEA’s Ultimate Test Generation Companion
TPV: A Tool for Validating Temporal Properties in UML Class Diagrams
TypeEvalPy: A Micro-benchmarking Framework for Python Type Inference Tools
ValidGen: A Tool for Automatic Generation of Validation Scripts to Support Rapid Requirements Validation
Verifying and Displaying Move Smart Contract Source Code for the Sui Blockchain

Call for Contributions

The ICSE 2024 Demonstrations Track aims to make the software engineering community aware of new advances in our field through compelling demonstrations that help advance research and practice. The track is a highly interactive venue where researchers and practitioners can demonstrate their tools and discuss them with attendees.

Tool-based demonstrations describe novel aspects of early prototypes or mature tools. The tool demonstrations must communicate clearly the following information to the audience:

  • the envisioned users;
  • the software engineering challenge it proposes to address;
  • the methodology it implies for its users; and
  • the results of validation studies already conducted for mature tools, or the design of planned studies for early prototypes.

Highlighting scientific contributions through concrete artifacts is a critical supplement to the traditional ICSE research papers. A demonstration provides the opportunity to communicate how the scientific approach has been implemented or how a specific hypothesis has been assessed, including details such as implementation and usage issues, data models and representations, and APIs for tool and data access. Authors of regular research papers are thus also encouraged to submit an accompanying demonstration paper. In such cases, the authors must ensure that the tool details should not have already been discussed in the original paper and the tool paper provides more information on implementation and usage.


Each submission will be reviewed by at least three members of the Demonstrations Track program committee. The evaluation criteria include:

  • the relevance of the proposed demonstration for the ICSE audience;
  • the technical soundness of the submission;
  • the originality of its underlying ideas;
  • the quality of its presentation in the associated video;
  • the potential applications and usefulness of the tool; and
  • the degree to which it considers the relevant literature.

How to Submit

Submissions must conform to the conference submission and formatting instructions (https://www.acm.org/publications/proceedings-template). In particular, submissions of demonstration papers must meet the following criteria: A demonstration submission may not exceed four pages for content and figures, with one page for references only.

Each submission must be accompanied by a short video (between three and five minutes long) illustrating the demonstration.

  • The submission must contain a link to the publicly available tool and its usage instructions. Optionally, if the tool is open-source, the submission should link the corresponding repository.
  • The video should be made available online at the time of submission. Videos should:
    1. provide an overview of the tool capabilities and/or dataset characteristics;
    2. walk through of (some of) the tool capabilities and/or data analysis process;
    3. where appropriate, provide clarifying voice-over and/or annotation highlights; and
    4. be engaging and exciting for the viewer!
  • A submission must not have been previously published in a demonstration form. The paper submission must be in PDF.

  • The tool demonstrations track will be using the single-anonymous reviewing model (the authors do not know who the reviewers are), so please include the authors’ identities in the submission materials.
  • Upon acceptance, authors have the possibility to separately submit their supplementary material to the ICSE 2024 Artifact Evaluation track, for recognition of artifacts that are reusable, available, replicated or reproduced.

Papers must be submitted electronically through the Demonstration Track submission site (https://icse2024-demo.hotcrp.com/). At the end of the abstract, make sure to append the URL at which your demo video can be found. Please note that, for consistency, we require that all videos be uploaded to YouTube and made accessible during the time of reviewing. Authors of successful submissions will have the opportunity to revise both the paper and the video (and its hosting location) by the camera-ready deadline.

For examples of previously successful short videos, please see the examples from ICSE 2018: https://www.youtube.com/playlist?list=PL6g5MCGbJtUF1iW4RSPvUtbKkemrVYrkP

Authors are encouraged to distribute their demonstration in an easy-to-use form, such as a virtual machine image, a software container (e.g., Docker), or a system configuration (e.g., Puppet, Ansible, Salt, CFEngine).

By submitting your article to an ACM Publication, you are hereby acknowledging that you and your co-authors are subject to all ACM Publications Policies, including ACM’s new Publications Policy on Research Involving Human Participants and Subjects. Alleged violations of this policy or any ACM Publications Policy will be investigated by ACM and may result in a full retraction of your paper, in addition to other potential penalties, as per ACM Publications Policy.

Please ensure that you and your co-authors obtain an ORCID ID, so you can complete the publishing process for your accepted paper. ACM has been involved in ORCID from the start and we have recently made a commitment to collect ORCID IDs from all of our published authors. The collection process has started and will roll out as a requirement throughout 2022. We are committed to improve author discoverability, ensure proper attribution and contribute to ongoing community efforts around name normalization; your ORCID ID will help in these efforts.

Important Dates (AOE Time)

Submission Deadline: 23-Oct-2023

Acceptance Notification: 20-Dec-2023

Camera Ready: 19-Jan-2024


Andrea Stocco, Technical University of Munich and fortiss, Germany

Tushar Sharma, Dalhousie University, Canada