Java Pathfinder on Android Devices

Abstract

Because Android apps are written in Java and executed on a virtual machine (VM), there is an opportunity to employ Java Pathfinder (JPF) for their verification. There already exist two JPF extensions, jpf-android and jpf-pathdroid. The former executes Java bytecode on the Java VM, while the latter executes Android applications in their original format. Both do not support native methods, and thus depend on a model of the Android environment. This paper introduces an alternative approach: we run JPF as an Android application that executes Java bytecode, which gives us direct access to the Android environment. This approach allows us to verify rich Android apps that rely on native calls

An automated Android exploratory testing based on code evolution coverage

“…JPF-Android [6], JPF-Mobile [7] and CATE [10] are model-based testing approaches. JPF-Android provides a simplified model of the Android framework on which an Android application can run.…”

“…Thus, it raised the need of starting from a solid ground to deliver a robust solution into our context. Thus, before we decided to develop and implement AETing, we evaluated the feasibility of reusing the following solutions: JPF-Android [6], JPF-Mobile [7], EHBDroid [8], DroidWalker [9] and CATE [10]. However, none of these solutions supported up-to-date Android versions, which is crucial in our context.…”