A Combined Technique of GUI Ripping and Input Perturbation Testing for Android Apps

Imparato, Gennaro

doi:10.1109/icse.2015.241

Cited by 10 publications

(5 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In this study, it was not allowed to inject faults into the SUT because this would represent a risk in the test environment for other projects, because there is a complex IT landscape and the applications are connected with each other. Hence we have used surrogate measures like coverage [1,18,21,22] to measure the percentage of the total code of an application has been tested with the test execution. In our study, effectiveness was measured in terms of:…”

Section: Effectivenessmentioning

confidence: 99%

See 1 more Smart Citation

Scriptless Testing at the GUI Level in an Industrial Setting

Chahim¹,

Duran

Vos

et al. 2020

Research Challenges in Information Science

View full text Add to dashboard Cite

and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights.• Users may download and print one copy of any publication from the public portal for the purpose of private study or research. • You may not further distribute the material or use it for any profit-making activity or commercial gain • You may freely distribute the URL identifying the publication in the public portal ? Take down policyIf you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediately and investigate your claim.

show abstract

Section: Effectivenessmentioning

confidence: 99%

“…Efficiency was measured by monitoring the time required for the test activities during the preparation, implementation, and evaluation phases. During the execution, all observations were also recorded in a working diary [1,8,12,13,[17][18][19][21][22][23][24]].…”

Section: Efficiencymentioning

confidence: 99%

Scriptless Testing at the GUI Level in an Industrial Setting

Chahim¹,

Duran

Vos

et al. 2020

Research Challenges in Information Science

View full text Add to dashboard Cite

show abstract

“…Gennaro Imparato [6] proposed GUI ripping technique with the combination of Input perturbation testing for improving the quality of Android Application. Now a day's mobile applications are becoming an integral part of our daily lives.…”

Section: B Architecture Design Phasementioning

confidence: 99%

GUI Test Script Repair in Regression Testing

Priya¹,

Rao²

2018

IJERMT

View full text Add to dashboard Cite

Abstract-UI testing is a process of testing a software application or functionality of GUI. It is defined as an interface between user and software which provides an easy way to interact with the system. GUI plays an important role in software engineering. GUI-based application requires that a test case consists of sequences of user actions/events to be executed. Selenium is an open-source tool for testing GUI Application by executing test cases whether the GUI Application is working properly or not. In this, we present test script repair technique to repair test cases. Test script repair technique uses reverse engineering process for creating the test script. Test script repair consists of three stages; they are Ripping, Mapping and Repairing. In ripping stage, there are two relationships for representing event interaction of GUI Application. During ripping we know the location of each widget. In mapping stage,original GUI events are mapped to an event-flow graph (EFG). In repairing stage, Event flow graph uses repairing transformations and human input to modified script to repair the test cases, and synthesizes a new "repaired" test script. During this process, test script repair uses GUI objects for yielding a final test script that can be executed using selenium tool to validate the GUI Application. An experiment using selenium tool to test, test cases suggests that it is effective in that unusable test scripts are repaired. Annotations significantly reduced the human cost to repair test cases.

show abstract

“…In 2015, Imparato [Imparato, 2015] implement an approach combining the GUI Ripping process with Input Perturbation Testing, i.e. it generates inputs for the test cases generated by the GUI Ripping tool.…”

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

A Combined Technique of GUI Ripping and Input Perturbation Testing for Android Apps

Cited by 10 publications

References 10 publications

Scriptless Testing at the GUI Level in an Industrial Setting

Scriptless Testing at the GUI Level in an Industrial Setting

GUI Test Script Repair in Regression Testing

Automated Pattern-Based Testing of Mobile Applications

Contact Info

Product

Resources

About