Show simple item record

dc.contributor.authorVentresque, Anthony
dc.contributor.authorLaurent, Thomas
dc.contributor.authorDoyle, Jordan
dc.date.accessioned2025-02-10T10:41:32Z
dc.date.available2025-02-10T10:41:32Z
dc.date.created10/08/2023en
dc.date.issued2023
dc.date.submitted2023en
dc.identifier.citationDoyle, Jordan, Laurent, Thomas, Ventresque, Anthony, Modelling Android applications through static analysis and systematic exploratory testing, International Conference on Dependable Systems and Their Applications (DSA), Tokyo, Japan, 10/08/2023, IEEE, 2023en
dc.identifier.otherY
dc.description.abstractMobile application development is a fast paced industry with frequent releases. While the development pace increases, so too does the need for automated test generation. Model-based test generation is one of the most common and successful approaches to support this need. Understanding and modelling the application under test is integral to producing comprehensive, dependable and effective tests. Unfortunately, mobile platforms such as Android, introduce a host of diffi- culties. Static analysis struggles with Android’s event-based nature and the growing variety of mechanisms available for developers to implement different features. Additionally, dy- namic analysis, implemented by popular random test genera- tors, is slow, inefficient, and limited by a lack of application knowledge. This paper introduces DroidGraph, a framework to generate a comprehensive control flow model of Android applications using traditional static analysis and efficient systematic ex- ploratory tests. DroidGraph provides a detailed model of an Android application, from low level method statements to high level user interface structures. This model can be used to support automated test generation. We apply DroidGraph to 19 diverse apps and show that our efficient exploratory tests, on average, interact with 18% more of the app than commonly used random exploration in 345 less interactions. Integrating the dynamic analysis results provided by these tests complements our static analysis, and uncovers on average 51 more components and 49% more interface callback links in the application code.en
dc.language.isoenen
dc.publisherIEEEen
dc.rightsYen
dc.subjectAutomated testingen
dc.subjectAndroid, Static analysis, Exploratory testingen
dc.titleModelling Android applications through static analysis and systematic exploratory testingen
dc.title.alternativeInternational Conference on Dependable Systems and Their Applications (DSA)en
dc.typeConference Paperen
dc.type.supercollectionscholarly_publicationsen
dc.type.supercollectionrefereed_publicationsen
dc.identifier.peoplefinderurlhttp://people.tcd.ie/ventresa
dc.identifier.peoplefinderurlhttp://people.tcd.ie/tlaurent
dc.identifier.peoplefinderurlhttp://people.tcd.ie/doylej51
dc.identifier.rssinternalid263711
dc.identifier.doihttp://dx.doi.org/10.1109/DSA59317.2023.00022
dc.rights.ecaccessrightsopenAccess
dc.identifier.orcid_id0000-0003-2064-1238
dc.status.accessibleNen
dc.identifier.urihttps://hdl.handle.net/2262/110811


Files in this item

Thumbnail
Thumbnail

This item appears in the following Collection(s)

Show simple item record