Testing Conformance of Life Cycle Dependent Properties of Mobile Applications

Franke, Dominik; Kowalewski, Stefan; Weise, Carsten; Prakobkosol, Nath

doi:10.1109/icst.2012.104

Cited by 19 publications

(20 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Yet each one of these approach has pros and cons. As an attempt to find an approach that amalgamates most benefits of the other approaches, Google attempts to introduce new modular phone [17]. Google's vision for a modular phone with working user-interchangeable components will allow the users to upgrade their mobile easily and efficiently.…”

Section: Discussionmentioning

confidence: 99%

Mobile Software Testing: Thoughts, Strategies, Challenges, and Experimental Study

Akour¹,

Falah²,

Al-Zyoud³

et al. 2016

ijacsa

View full text Add to dashboard Cite

Abstract-Mobile devices have become more pervasive in our daily lives, and are gradually replacing regular computers to perform traditional processes like Internet browsing, editing photos, playing videos and sound track, and reading different files. The importance of mobile devices in our life necessitates more concerns of the reliability and compatibility of mobile applications, and thus, testing these applications arises as an important phase in mobile devices adaption process. This paper addressed various research directions on mobile applications testing by investigating essential concepts, scope, features and requirements for testing mobile application. We highlight the similarities and the differences between mobile APP testing and mobile web testing. Furthermore, we discuss and compare different mobile testing approaches and environments, and provide the challenges as emergent needs in test environments. As a case study, we compared the testing experience of hybrid application in an emulator and a real world device. The purpose of the experiment is to verify to which extent a virtual device can emulate a complete client experience. Set of experiments are conducted where five android mobile browsers are tested. Each browser will be on a real device as well as an emulated device with the same features (CPU used, memory size, etc). The application will be tested on the following metrics: Performance and function/behavior testing.

show abstract

Section: Discussionmentioning

confidence: 99%

Mobile Software Testing: Thoughts, Strategies, Challenges, and Experimental Study

Akour¹,

Falah²,

Al-Zyoud³

et al. 2016

ijacsa

View full text Add to dashboard Cite

show abstract

“…Other studies - [4] and [5] that include the clear distinction between the platforms, concentrate on some narrow topic. On the other side, there are different iOS testing checklists, mind maps, blogs etc.…”

Section: Introduction According To Clearwater Technology Mobile Compumentioning

confidence: 99%

iOS Applications Testing

Kulesovs

2015

ETR

View full text Add to dashboard Cite

show abstract

“…Otherwise, the testing process is prone to only finding crashes. However, the type of information the model/oracle contains differs according to the final goal: it may contain the correct behaviour of the AUT (e.g., Nguyen et al [Nguyen et al, 2012]), or the life cycle an application should follow (e.g., Franke et al [Franke et al, 2012a]) or the correct filtering of intents (e.g., Avancini and Ceccato [Avancini & Ceccato, 2013]) or even information on how to classify the purpose of the application according to its description (e.g., Gorla et al [Gorla et al, 2014]). The output of the approaches is either a test suite (when the goal is to generate test cases) or the result of the test itself.…”

Section: Brief Summarymentioning

confidence: 99%

“…Franke et al [Franke et al, 2012a] present an approach to test how mobile applications handle the life cycles of their activities. Even though they use unit testing [IEEE, 1990], they do not consider an unit as being the smallest part of an application as it is not possible to test the life cycle of methods or interfaces.…”

Section: Reliabilitymentioning

confidence: 99%

Automated Pattern-Based Testing of Mobile Applications

Morgado

Paiva

Faria

2014

2014 9th International Conference on the Quality of Information and Communications Technology

View full text Add to dashboard Cite

Testing is essential to improve the quality of a product and is, thus, a crucial part of any development process. However, the amount of time and resources companies dedicate to it is usually reduced, which justifies the high focus of the community on improving testing automation. Considering the importance smartphones have acquired in our daily lives, it is extremely important to define techniques to test mobile applications in order to ensure their quality.This document presents a testing approach and tool (iMPAcT) to improve the automation of mobile testing based on the presence of recurring behaviour, UI Patterns. It combines reverse engineering, pattern matching and testing. The reverse engineering process is responsible for crawling the application, i.e. to analyse the state of the application and to interact with it by firing events. The pattern matching tries to identify the presence of UI patterns based on a catalogue of patterns. When a UI Pattern from the catalogue is detected, a test strategy is applied. These test strategies are called UI Test Patterns. These three phases work in an iterative way: the patterns and identified and tested between firing of events, i.e. the process alternates between exploring the application and testing the UI Patterns. The process is dynamic and fully automatic not requiring any previous knowledge about the application under test.A catalogue of patterns is presented in this document. It has UI Patterns to identify on mobile applications and UI Test Patterns defining generic test strategies to test them. These patterns are generic and, thus, can be applied to any application.In order to validate the overall approach we have conducted three experiments. The goal is to analyse the capacity of iMPAcT of finding failures and assess if the results are reliable. In addition, we also measured the execution time and events coverage. Este documento apresenta uma abordagem de teste, e respetiva ferramenta (iMPAcT), para melhorar a automação de teste de aplicações móveis baseado na presença de comportamento recorrente, padrões de UI. Esta abordagem combina engenharia reversa, deteção de padrões e teste. O processo de engenharia reversa é responsável pela exploração da aplicação, ou seja, pela análise do estado da aplicação e a interação com ela através de eventos. O processo de deteção de padrões baseia-se num catálogo de padrões para identificar padrões de UI. Quando um padrão de UI do catálogo é detetado, uma estratégia de teste é aplicada. Estas estratégias de teste denominam-se padrões de teste. Estas três fases trabalham de forma iterativa: os padrões são identificados e testados entre eventos, ou seja, o processo alterna entre a exploração da aplicação e o teste dos padrões de UI. O processo é dinâmico e completamente automático e não necessita de qualquer conhecimento prévio acerca da aplicação a testar.Um catálogo de padrões é apresentado neste documento. Contém padrões de UI para serem identificados em aplicações móveis e padrões de teste que definem estratégias ...

show abstract

Testing Conformance of Life Cycle Dependent Properties of Mobile Applications

Cited by 19 publications

References 3 publications

Mobile Software Testing: Thoughts, Strategies, Challenges, and Experimental Study

Mobile Software Testing: Thoughts, Strategies, Challenges, and Experimental Study

iOS Applications Testing

Automated Pattern-Based Testing of Mobile Applications

Contact Info

Product

Resources

About