π€ AI Summary
This study addresses the challenge of migrating Android GUI test cases to OpenHarmony, a process hindered by high costs and the absence of targeted methodologies. It presents the first systematic investigation of this migration problem, introducing ATHβa benchmark dataset comprising 36 commercial applications and 108 test casesβand evaluates existing approaches ReSPlay and ITeM. Analysis reveals that architectural and ecosystem disparities between Android and OpenHarmony are primary causes of migration failure. To overcome these limitations, the authors propose ITeM-HM, an enhanced method incorporating OpenHarmony-specific characteristics. Evaluated on ATH, ITeM-HM significantly improves migration success rates from 15% (ReSPlay) and 26% (ITeM) to 81%, achieving a relative improvement of 214%.
π Abstract
To reduce the substantial engineering effort required to test the corresponding applications from Android to OpenHarmony, migrating existing GUI test cases has become a critical problem. However, current research neither proposes solutions tailored for OpenHarmony nor provides a systematic evaluation of migration approaches on this system, leaving developers with limited empirical guidance in practice. In this paper, we present the first systematic empirical study of test migration from Android to OpenHarmony. Specifically, we first construct a dataset referred to as the ATH Benchmark, comprising 36 commercial applications with an average of over 9 billion downloads, along with 108 manually designed test cases. Second, we select two state-of-the-art test migration approaches (i.e., ReSPlay and ITeM) and adapt these two approaches to enable their execution on OpenHarmony. Third, we use the preceding infrastructure to evaluate these two approaches from three perspectives, including testing performance, root causes of failures, and the impact of OpenHarmony characteristics. Our results reveal that existing test migration approaches are less effective (15% success-rate on ReSPlay and 26% success-rate on ITeM) in Android-to-OpenHarmony scenarios. Through an in-depth analysis of failed cases, we identify that test performance is primarily hindered by OpenHarmony-specific characteristics, including technical architecture differences and unique ecosystem traits. Utilizing these findings, we propose an enhanced approach based on ITeM, referred as ITeM-HM, which incorporates specific OpenHarmony system features. As a result, ITeM-HM successfully achieves a 214% success-rate relative improvement over the original ITeM (from 26% to 81%).