Pooja Rani

Pooja Rani

Auto-generated profile, based on publicly available information

Pooja Rani

Department of Informatics, University of Zürich, Zürich, Switzerland

Research Focus & Metrics

Academic Career Length

6Years (2021-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
22 September 2022 in Journal of Systems and Software
Verified
Journal Article
Open access
PRPooja Rani
Pooja Rani
ABArianna Blasi
Arianna Blasi
NSNataliia Stulova
Nataliia Stulova
SPSebastiano Panichella
Sebastiano Panichella
AGAlessandra Gorla
Alessandra Gorla
ONOscar Nierstrasz
Oscar Nierstrasz

24 May 2025 in ACM Transactions on Software Engineering and Methodology
Verified
Journal Article
Open access
CBChristian Birchler
Christian Birchler
SKSajad Khatiri
Sajad Khatiri
PRPooja Rani
Pooja Rani
TKTimo Kehrer
Timo Kehrer
SPSebastiano Panichella
Sebastiano Panichella
As the era of autonomous cyber-physical systems (ACPSs), such as unmanned aerial vehicles and self-driving cars, unfolds, the demand for robust testing methodologies is key to realizing the adoption of such systems in real-world scenarios. However, traditional software testing paradigms face unprecedented challenges in ensuring the safety and reliability of these systems. In response, this article pioneers a strategic roadmap for simulation-based system-level testing of ACPSs, specifically focusing on autonomous systems. Our article discusses the relevant challenges and obstacles of ACPSs, focusing on test automation and quality assurance, hence advocating for tailored solutions to address the unique demands of autonomous systems. While providing concrete definitions of test cases within simulation environments, we also accentuate the need to create new benchmark assets and the development of automated tools tailored explicitly for autonomous systems in the software engineering community. This article not only highlights the relevant, pressing issues the software engineering community should focus on (in terms of practices, expected automation, and paradigms), but it also outlines ways to tackle them. By outlining the various domains and challenges of simulation-based testing/development for ACPSs, we provide directions for future research efforts.

12 July 2024 in Proceedings of the ACM on Software Engineering
Verified
Journal Article
Open access
CBChristian Birchler
Christian Birchler
TMTanzil Kombarabettu Mohammed
Tanzil Kombarabettu Mohammed
PRPooja Rani
Pooja Rani
TNTeodora Nechita
Teodora Nechita
TKTimo Kehrer
Timo Kehrer
SPSebastiano Panichella
Sebastiano Panichella
Software metrics such as coverage or mutation scores have been investigated for the automated quality assessment of test suites. While traditional tools rely on software metrics, the field of self-driving cars (SDCs) has primarily focused on simulation-based test case generation using quality metrics such as the out-of-bound (OOB) parameter to determine if a test case fails or passes. However, it remains unclear to what extent this quality metric aligns with the human perception of the safety and realism of SDCs. To address this (reality) gap, we conducted an empirical study involving 50 participants to investigate the factors that determine how humans perceive SDC test cases as safe, unsafe, realistic, or unrealistic. To this aim, we developed a framework leveraging virtual reality (VR) technologies, called SDC-A labaster , to immerse the study participants into the virtual environment of SDC simulators. Our findings indicate that the human assessment of safety and realism of failing/passing test cases can vary based on different factors, such as the test’s complexity and the possibility of interacting with the SDC. Especially for the assessment of realism, the participants' age leads to a different perception. This study highlights the need for more research on simulation testing quality metrics and the importance of human perception in evaluating SDCs.

14 April 2024
Verified
Conference Paper
Open access
PRPooja Rani
Pooja Rani
JZJonas Zellweger
Jonas Zellweger
VKVeronika Kousadianos
Veronika Kousadianos
LCLuis Cruz
Luis Cruz
TKTimo Kehrer
Timo Kehrer
ABAlberto Bacchelli
Alberto Bacchelli
As the energy footprint generated by software is increasing at an alarming rate, understanding how to develop energy-efficient applications has become a necessity. Previous work has introduced catalogs of coding practices, also known as energy patterns. These patterns are yet limited to Mobile or third-party libraries. In this study, we focus on the Web domain---a main source of energy consumption. First we investigated whether and how Mobile energy patterns can be ported to this domain and found that 20 patterns could be ported. Then, we interviewed six expert web developers from different companies to challenge the ported patterns. Most developers expressed concerns for antipatterns, specifically with functional antipatterns, and were able to formulate guidelines to locate these patterns in the source code. Finally, to quantify the effect of Web energy patterns on energy consumption, we set up an automated pipeline to evaluate two ported patterns: 'Dynamic Retry Delay' (DRD) and 'Open Only When Necessary' (OOWN). With this, we found no evidence that the DRD pattern consumes less energy than its antipattern, while the opposite is true for OOWN. Data and Material: https://doi.org/10.5281/zenodo.8404487


18 August 2021 in Empirical Software Engineering
Verified
Journal Article
Open access
PDF file
PRPooja Rani
Pooja Rani
SPSebastiano Panichella
Sebastiano Panichella
MLManuel Leuenberger
Manuel Leuenberger
MGMohammad Ghafari
Mohammad Ghafari
ONOscar Nierstrasz
Oscar Nierstrasz
Context: Previous studies have characterized code comments in various programming languages, showing how high quality of code comments is crucial to support program comprehension activities, and to improve the effectiveness of maintenance tasks. However, very few studies have focused on understanding developer practices to write comments. None of them has compared such developer practices to the standard comment guidelines to study the extent to which developers follow the guidelines.Objective: Therefore, our goal is to investigate developer commenting practices and compare them to the comment guidelines.Method: This paper reports the first empirical study investigating commenting practices in Pharo Smalltalk. First, we analyze class comment evolution over seven Pharo versions. Then, we quantitatively and qualitatively investigate the information types embedded in class comments. Finally, we study the adherence of developer commenting practices to the officialclass comment templateover Pharo versions.Results: Our results show that there is a rapid increase in class comments in the initial three Pharo versions, while in subsequent versions developers added comments to both new and old classes, thus maintaining a similar code to comment ratio. We furthermore found three times as many information types in class comments as those suggested by the template. However, the information types suggested by the template tend to be present more often than other types of information. Additionally, we find that a substantial proportion of comments follow the writing style of the template in writing these information types, but they are written and formatted in a non-uniform way.Conclusion: The results suggest the need to standardize the commenting guidelines for formatting the text, and to provide headers for the different information types to ensure a consistent style and to identify the information easily. Given the importance of high-quality code comments, we draw numerous implications for developers and researchers to improve the support for comment quality assessment tools.