Abstract
Testing of GUI (Graphical User Interface) applications has many challenges due to its event driven nature and infinite input domain. It is very difficult for any programmer to test for each and every possible input. When test cases are generated using automated testing tool it uses each and every possible combination to generate test cases hence generates numerous number of test case for any GUI based application. Within a defined time frame it is not possible to test every test case, that is why test cases prioritization is required. Test-case prioritization has been widely proposed and used in recent years as it can improve the rate of fault detection during the testing phase. Very few methods are defined for GUI Test case prioritization that usually consider single criteria for assigning priority for the test case which is not sufficient for the consideration of that test case as more fault revealing. In this paper we have proposed a method for assigning weight value on the basis of multiple factors as one of the criteria for test case prioritization for GUI based software. These factors are: The type of event, Event Interaction, and Parameter-value interaction coverage-based criteria. In the proposed approach priority is assigned based upon these factors using fuzzy logic model. Experimental results indicate that the proposed model is suitable for prioritizing the test cases of GUI based software.
Highlights
Testing is widely recognized as a key quality assurance (QA) activity in the software development process
The results show that test case prioritization by 2-way and PVLtoS (Parameter count based criteria) provided best improvement in the rate of fault detection for graphical user interfaces (GUIs) based software
In this paper we have proposed a fuzzy model with three inputs, namely Type of event, Event Interaction, Count based criteria
Summary
Testing is widely recognized as a key quality assurance (QA) activity in the software development process. Testing of graphical user interfaces (GUIs) was a neglected research area till last decade [4]. Most of the test case generation techniques require human involvement and are resource intensive. Running all GUI test cases and fixing all bugs may be time consuming and delaying the project completion. This would require that the test developed for one version should be reusable across various versions [1, 4]. This paper is organized as follows: Section II describes the research background for the proposed work.
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
