{'fraction_non_alphanumeric': 0.010700389105058366, 'fraction_numerical': 0.0, 'mean_word_length': 5.274390243902439, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
An Approach to Test Classification in Big Android Applications

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.