CSC/ECE 517 Fall 2009/wiki2 10 28: Difference between revisions
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
== Challenges in GUI testing == | == Challenges in GUI testing == | ||
Testing Graphical User Interfaces (GUI) is a difficult task because GUI possesses a large number of states that are to be tested; the input space is extremely large due to different permutations of inputs and events and also there are complex GUI dependencies, which may exist. | |||
'''Input domain:'''Testing graphical user interface requires different permutations of input. This not only increases the complexity but also the input size domain. These inputs are users interactions or events while output could be an event or some graphical object [8].Also, one state of GUI may depend on many other states. This further increases the difficulty in GUI testing. | |||
<br> | |||
'''Sequences:''' - | |||
<br> | |||
'''Regression testing:''' | |||
<br> | |||
'''Maintainence''' | |||
<br> | |||
'''Event driven nature:''' Users have full control while using graphical user interface. This leads to many user inputs and multiple windows to be opened. Also, there could be many events like user clicking textbox field or a button and since user has many available options, large number | |||
== References == | == References == | ||
[1] http://en.wikipedia.org/wiki/Graphical_user_interface <br> | [1] http://en.wikipedia.org/wiki/Graphical_user_interface <br> | ||
Revision as of 00:28, 10 October 2009
GUI testing frameworks
GUI is a graphical user interface [1] that allows users to interact with the system. The user has more natural approach to the applications and feels more in control of the system. Today, every application provides GUI support and its easy to use feature is making it popular among users. The process of testing the user interface to test if it meets its specification is called GUI testing [2].
Challenges in GUI testing
Testing Graphical User Interfaces (GUI) is a difficult task because GUI possesses a large number of states that are to be tested; the input space is extremely large due to different permutations of inputs and events and also there are complex GUI dependencies, which may exist.
Input domain:Testing graphical user interface requires different permutations of input. This not only increases the complexity but also the input size domain. These inputs are users interactions or events while output could be an event or some graphical object [8].Also, one state of GUI may depend on many other states. This further increases the difficulty in GUI testing.
Sequences: -
Regression testing:
Maintainence
Event driven nature: Users have full control while using graphical user interface. This leads to many user inputs and multiple windows to be opened. Also, there could be many events like user clicking textbox field or a button and since user has many available options, large number
References
[1] http://en.wikipedia.org/wiki/Graphical_user_interface
[2] http://en.wikipedia.org/wiki/GUI_software_testing
[3] http://www.gerrardconsulting.com/GUI/TestGui.html
[4] http://en.wikipedia.org/wiki/List_of_GUI_testing_tools
[5] http://www.geocities.com/xtremetesting/TestingDictionary.html#S
[6] GUI Ripping: Reverse Engineering of Graphical User Interfaces for Testing, Ishan Banerjee, Adithya Nagarajan, and Atif Memon
[7] http://www.cs.umd.edu/~atif/papers/MemonIEEEComputer2002.pdf
[8] Lee J. White, "Regression Testing of GUI Event Interactions," icsm, pp.350, 12th International Conference on Software Maintenance (ICSM'96), 1996