Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Towards automated translation between generations of GUI-based tests for mobile devices
Politecnico di Torino, ITA.
Politecnico di Torino, ITA.
Politecnico di Torino, ITA.
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.
2018 (English)In: Companion Proceedings for the ISSTA/ECOOP 2018 Workshops, Association for Computing Machinery, Inc , 2018, p. 46-53Conference paper, Published paper (Refereed)
Abstract [en]

Market demands for faster delivery and higher software quality are progressively becoming more stringent. A key hindrance for software companies to meet such demands is how to test the software due to to the intrinsic costs of development, maintenance and evolution of testware. Especially since testware should be defined, and aligned, with all layers of system under test (SUT), including all graphical user interface (GUI) abstraction levels. These levels can be tested with different generations of GUI-based test approaches, where 2nd generation, or Layout-based, tests leverage GUI properties and 3rd generation, or Visual, tests make use of image recognition. The two approaches provide different benefits and drawbacks and are seldom used together because of the aforementioned costs, despite growing academic evidence of the complementary benefits. In this work we propose the proof of concept of a novel two-step translation approach for Android GUI testing that we aim to implement, where a translator first creates a technology independent script with actions and elements of the GUI, and then translates it to a script with the syntax chosen by the user. The approach enables users to translate Layout-based to Visual scripts and vice versa, to gain the benefits (e.g. robustness, speed and ability to emulate the user) of both generations, whilst minimizing the drawbacks (e.g. development and maintenance costs). We outline our approach from a technical perspective, discuss some of the key challenges with the realization of our approach, evaluate the feasibility and the advantages provided by our approach on an open-source Android application, and discuss the potential industrial impact of this work. © 2018 ACM.

Place, publisher, year, edition, pages
Association for Computing Machinery, Inc , 2018. p. 46-53
Keywords [en]
Android (operating system), Computer software selection and evaluation, Costs, Graphical user interfaces, Image recognition, Open source software, Testing, Abstraction level, Android applications, Automated translation, Graphical user interfaces (GUI), Proof of concept, Software Quality, System under test, Technology independent, Software testing
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:bth-17623DOI: 10.1145/3236454.3236488Scopus ID: 2-s2.0-85060987331ISBN: 9781450359399 (print)OAI: oai:DiVA.org:bth-17623DiVA, id: diva2:1290693
Conference
2018 International Symposium on Software Testing and Analysis, ISSTA 2018, Amsterdam, 16 July 2018 through 21 July 2018
Available from: 2019-02-21 Created: 2019-02-21 Last updated: 2019-02-21Bibliographically approved

Open Access in DiVA

No full text in DiVA

Other links

Publisher's full textScopus

Authority records BETA

Alégroth, Emil

Search in DiVA

By author/editor
Alégroth, Emil
By organisation
Department of Software Engineering
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar

doi
isbn
urn-nbn

Altmetric score

doi
isbn
urn-nbn
Total: 55 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf