An Approach to Test Classification in Big Android Applications

Thomas Hirsch, Christian Schindler, Matthias Müller, Thomas Schranz, Wolfgang Slany

Research output: Chapter in Book/Report/Conference proceedingConference paperpeer-review

Abstract

This paper intends to shed some light on how to approach challenges on automated test strategies and architecture that arise in big Android applications. The Android documentation and Google testing recommendations are overly simplistic and showcase only trivial and small examples, while the real challenges in testing big Android applications stay untouched. We discuss testing partitioning, classification of tests, and the application of the test pyramid on the Android platform. Besides a small exploratory study on the testing situation in a limited sample of open source Android applications, we show the consequences of a bad test strategy and technical debt in a big and long running Android project in the case of Catrobat. By Identifying anti patterns and smells, we establish general guidelines and patterns for testing big Android applications, as well as metrics for test code quality which have been applied and found useful in the Catrobat project.
Original languageEnglish
Title of host publication 2019 IEEE 19th International Conference on Software Quality, Reliability and Security Companion (QRS-C)
PublisherIEEE Computer Society Conference Publishing Services
ChapterSoftware Engineering and Knowledge Management
Pages300-308
Number of pages9
ISBN (Electronic)978-1-7281-3925-8
DOIs
Publication statusPublished - 2019
Event19th IEEE International Conference on Software Quality, Reliability, and Security Companion, QRS-C 2019 - Sofia, Bulgaria
Duration: 22 Jul 201926 Jul 2019

Conference

Conference19th IEEE International Conference on Software Quality, Reliability, and Security Companion, QRS-C 2019
Abbreviated titleQRS-C 2019
Country/TerritoryBulgaria
CitySofia
Period22/07/1926/07/19

Fingerprint

Dive into the research topics of 'An Approach to Test Classification in Big Android Applications'. Together they form a unique fingerprint.

Cite this