Design and Assessment of Software Testing Technique for Event Driven Softwar

Abstract

Testing is widely recognized as a key Quality Assurance (QA) activity in the software newlinedevelopment process. Graphical User Interface (GUI) constitutes as much as 45-60% of the total newlinesoftware code in any software, so testing of GUI is a very important concern. Most of the test newlinecase generation techniques require human involvement and are resource intensive. Many newlineautomated approaches were proposed for test case generation but in practice capture replay tools newlineare used which increases the cost of test case generation. Due to event driven nature of GUI, it newlinetakes sequence of events as input and after change of state, generates new sequence of input as newlineoutput. For different set of state and combination of inputs, GUI generates different outputs. It newlinewould be difficult to manage all the combinations for testing as number of combinations grows newlineexponentially with the number of events. Running all GUI test cases and then fixing all bugs can newlinebe time consuming and delays the project completion. Regression Testing is a performed to newlineensure modified code does not have any unintended side effect on the software. If regression newlinetesting is performed with retest-all method it will be very time consuming as testing activity. newlineTherefore test suite reduction methods are used to reduce the size of original test suite. Test suite newlinereduction and prioritization are two different approaches to manage test suites during regression newlinetesting. It is important to prioritize the test cases that uncover the most faults as fast as possible newlinein the testing process. There is a requirement of a process which reduces the size of test suite in newlineregression testing process. In order to develop test suite prioritization and reduction technique, newlinewe need to identify metrics which have effect on testability of event driven software.