English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

Despite being one of the largest and most popular projects, the officialAndroid framework has only provided test cases for less than 30% of its APIs.Such a poor test case coverage rate has led to many compatibility issues thatcan cause apps to crash at runtime on specific Android devices, resulting inpoor user experiences for both apps and the Android ecosystem. To mitigate thisimpact, various approaches have been proposed to automatically detect suchcompatibility issues. Unfortunately, these approaches have only focused ondetecting signature-induced compatibility issues (i.e., a certain API does notexist in certain Android versions), leaving other equally important types ofcompatibility issues unresolved. In this work, we propose a novel prototypetool, JUnitTestGen, to fill this gap by mining existing Android API usage togenerate unit test cases. After locating Android API usage in given real-worldAndroid apps, JUnitTestGen performs inter-procedural backward data-flowanalysis to generate a minimal executable code snippet (i.e., test case).Experimental results on thousands of real-world Android apps show thatJUnitTestGen is effective in generating valid unit test cases for Android APIs.We show that these generated test cases are indeed helpful for pinpointingcompatibility issues, including ones involving semantic code changes.

Mining Android API Usage to Generate Unit Test Cases for Pinpointing Compatibility Issues