CrossBot: Android GUI Testing via Efficient Cross-Device History Reuse

Authors:

Abstract
Context: Android applications are increasingly released as multiple device-specific variants, such as phone, tablet, in-vehicle, and TV versions. Existing automated GUI testing tools usually test these variants independently, repeatedly spending testing budget on common functionality and providing little guidance when a new phone variant is explored.Objectives: This paper aims to improve phone-target Android GUI testing by reusing testing histories collected offline from non-phone variants of the same app, while remaining robust to cross-device differences in layouts, widgets, and interaction flows.Methods: We present \texttt{CrossBot}, a widget-level history reuse framework. \texttt{CrossBot} summarizes source-side testing histories as probabilistic event-to-widget transition priors, matches semantically corresponding widgets across device variants using text, resource-id, and activity context, and injects the transferred priors into online phone-side exploration. To reduce online overhead, \texttt{CrossBot} further applies embedding caching and locality-sensitive hashing. We evaluate \texttt{CrossBot} on 14 commercial Android apps under Tablet-to-Phone, TV-to-Phone, Car-to-Phone, and Multi-to-Phone reuse settings.Results: Compared with \texttt{Fastbot2}, \texttt{CrossBot-With-X} improves activity coverage by 16.5\%--24.2\% and widget coverage by 62.0\%--88.5\% at 60 minutes. It also outperforms a resource-ID-only reuse baseline and sustains coverage growth in four-hour sessions. In the LSH ablation, LSH-backed matching increases throughput by 97.3\% and reduces amortized cost by 46.8\% on average.Conclusion: The results show that widget-level cross-device history reuse can effectively guide phone-target GUI exploration under UI differences, and that efficient approximate matching makes such reuse practical for long-running Android testing.