Page 73 - SOFTWARE TESTING & QUALITY ASSURANCE
P. 73

Software Testing and Quality Assurance



                          Some of the reasons for the popularity of the GUI are:
                           1.   It is easy to understand visual interface.
                           2.   It is flexible to use in most of the application areas.
                           3.   It is helpful for people who have difficulty in typing.

                           4.   It provides visibility of multiple windows, to handle information in a better way.
                           5.   It helps in controlling the screens as per user’s choice.
                           6.   It facilitates exchange of information  because of  integration of the packaged  and customized
                               applications.
                          Although GUI has simplified things for users, it has complicated them for a developer. GUI testing can
                          be performed either manually or automatically. Manual testing is a time consuming process, which is
                          performed without the help of automated tools like winruuner, silk test, and Quick Test Professional
                          (QTP). Automated testing is performed by using  automated tools like load runner, winruuner and
                          Quick Test Professional (QTP).


                          Did you know?   A Windows based application testing can be classified into Standardization Testing,
                                        GUI Testing, Validation Testing, and Functionality Testing.
                          GUI testing is commonly known as usability testing or user interface testing.  Usability testing is the
                          process of checking a product’s compatibility, when in use. After completion of the testing process, the
                          software product is released  to a set of users  as a  beta version or a pre-release  version. The users
                          evaluate and assess the performance of the software based on customer experience.
                          GUI testing comprises four stages, the details of which are shown in Table 5.1.

                           1.   Low level
                           2.   Application
                           3.   Integration
                           4.   Non-functional

                                                        Table 5.1 GUI Testing Stages


                                               Stages                        Testing Involved
                                  Low Level Stage                  Checklist testing
                                                                   Navigation
                                  Application                      Equivalence partitioning
                                                                   Boundary values
                                                                   Decision tables
                                                                   State transition testing
                                  Integration                      Desktop integration
                                                                   Communication
                                                                   Synchronization

                                  Non-Functional                   Soak testing
                                                                   Compatibility testing
                                                                   Platform/environment

                          Source: http://www.comparesuite.com/solutions/tests-automation/hb_gui_testing_introduction.htm







                          66                      LOVELY PROFESSIONAL UNIVERSITY
   68   69   70   71   72   73   74   75   76   77   78