GUI Testing: Challenges, Methods, and Coverage, Schemes and Mind Maps of Software Engineering

Download GUI Testing: Challenges, Methods, and Coverage and more Schemes and Mind Maps Software Engineering in PDF only on Docsity!

Software Verification and Validation

Lecture No. 20

Module 149: Graphical User Interface (GUI) Testing

GUI Testing

 GUI testing is a process of

verifying the GUI for its

compliance with

specifications, general

principles, and specific

project requirements.

 It involves simulating user

actions like clicking buttons,

following links, and other

similar actions.

 In this way, developers check

the product for its correct

operation, mutual interaction

of components, and the UI

usability as a whole.

GUI Testing

 GUI can exercise remote

code

 GUI responds to user events

(e.g., mouse clicks)

 UIs are event-driven

systems

 Testing GUI correctness is

critical for system usability,

robustness and safety

 The whole system can be

executed by means of the

GUI

Module 150: Graphical User Interface (GUI) Testing Challenges

GUI Testing Challenges

 Testing correctness of a GUI

is difficult for a number of

reasons.

 First of all, space of possible

interactions with a GUI is

enormous

 The large number of

possible states results in a

large number of input

permutations requiring

extensive testing,

GUI Testing Challenges

 Infinitely Many

 Randomly Choose

Sequences

 Expert Chooses Sequences

 Automatically Generate

Events for commonly used

taks

Initial State Goal State Multiple Event Sequences This is the text. (^) This is the text.

GUI Testing Challenges

Initial

State

Goal

State

This is the text.

This is the text.

GUI Testing Challenges  (^) Problem of Coverage  (^) For conventional software, coverage is measured using amount and type of underlying code exercised.  (^) These measures do not hold good for GUI based testing.  (^) Another issue that we need to tackle is related to which level we are conducting the testing?  (^) Unit  (^) Integration  (^) System  (^) Regression

GUI Testing Challenges

 How to choose inputs?

 using specifications

or use cases etc.

 using code

 only considering

GUI (functionality,

structure)

 (^) How to identify the expected output?  (^) test oracles  (^) How good test cases are?  (^) when we can stop the testing activity

GUI Testing Challenges  (^) Coverage:  (^) Cannot use code-based coverage  (^) Source code not always available  (^) Event-based input  (^) Different level of abstraction  (^) We define an event-based graph for coverage  (^) We call in Event-flow Graph.. END

Module 151: GUI Testing Methods

GUI Testing Methods  (^) Model-based GUI testing:  (^) A graphical description of the behaviour of the system is known as a Model.  (^) A model helps us to determine system behaviour under test.  (^) We use system requirements in order to generate the efficient test cases Develop a model.  (^) Determine various inputs for this model.

GUI Testing Methods

 Determine expected

output for this model.

 Execute the tests.

 Compare the actual

result against the

expected output.

 Make the decision on the

action on the model.

 Since GUI is event based

 We develop model in

terms of an event-flow

graph