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

Validation of Android apps via testing is difficult owing to the presence offlaky tests. Due to non-deterministic execution environments, a sequence ofevents (a test) may lead to success or failure in unpredictable ways. In thiswork, we present an approach and tool FlakeShovel for detecting flaky teststhrough systematic exploration of event orders. Our key observation is that fora test in a mobile app, there is a testing framework thread which creates thetest events, a main User-Interface (UI) thread processing these events, andthere may be several other background threads running asynchronously. For anyevent e whose execution involves potential non-determinism, we localize theearliest (latest) event after (before) which e must happen.We then efficientlyexplore the schedules between the upper/lower bound events while groupingevents within a single statement, to find whether the test outcome is flaky. Wealso create a suite of subject programs called DroidFlaker to study flaky testsin Android apps. Our experiments on subject-suite DroidFlaker demonstrate theefficacy of our flaky test detection. Our work is complementary to existingflaky test detection tools like Deflaker which check only failing tests.FlakeShovel can detect flaky tests among passing tests, as shown by ourapproach and experiments.

Concurrency-related Flaky Test Detection in Android apps