2017
DOI: 10.1002/stvr.1629
|View full text |Cite
|
Sign up to set email alerts
|

Pattern‐based GUI testing: Bridging the gap between design and quality assurance

Abstract: Software systems with a graphical user interface (GUI) front end are typically designed using user interface (UI) Patterns, which describe generic solutions (with multiple possible implementations) for recurrent GUI design problems. However, existing testing techniques do not take advantage of this fact to test GUIs more efficiently. In this paper, we present a new pattern-based GUI testing (PBGT) approach that formalizes the notion of UI Test Patterns, which are generic test strategies to test UI patterns ove… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 25 publications
(5 citation statements)
references
References 25 publications
0
5
0
Order By: Relevance
“…Automating GUI testing is difficult but important, and therefore a subject of intense research and development (e.g. [15,197] and references therein). Tests need to sample the input space, which consists of external data, parameterization, and user actions like mouse movements, clicks, and keyboard inputs.…”
Section: Gui Testsmentioning
confidence: 99%
“…Automating GUI testing is difficult but important, and therefore a subject of intense research and development (e.g. [15,197] and references therein). Tests need to sample the input space, which consists of external data, parameterization, and user actions like mouse movements, clicks, and keyboard inputs.…”
Section: Gui Testsmentioning
confidence: 99%
“…There are various MBGT approaches, for example, using Spec Explorer in a tool chain [35], NModel tool [36], pattern‐based GUI testing [37], Finite State Machine (FSMs) to test web applications [38] and TEMA tools for testing Android applications [39], trying to reduce both the initial effort in creating the test scripts and the maintenance effort required after each change in the GUI. The difference to the script‐based testing is that in model‐based approaches the scripts are automatically generated.…”
Section: Script‐based Graphical User Interface Test Automationmentioning
confidence: 99%
“…Another drawback is that many recording tools record human interactions by hooking into the SUT and capturing its responses, which may not be possible to replay, leading to failed test cases. The R&R tools were also limited by their underlying technologies that made the test cases brittle [5], [9]. This brittleness caused tests to require significant maintenance efforts that diminished their return on investment.…”
Section: Fig 3 Screenshot Of the Scout Prototypementioning
confidence: 99%