Page 68 - SOFTWARE TESTING & QUALITY ASSURANCE
P. 68

Sarabjit Kumar, Lovely Professional University            Unit 5: Special Types of Testing



                                    Unit 5: Special Types of Testing



               CONTENTS
               Objectives
               Introduction
               5.1 Configuration Testing
                     5.1.1   Overview of Configuration Testing
                     5.1.2   Identifying Software Configuration
                     5.1.3   Deciding the Hardware Configuration
               5.2 Graphical User Interface Testing

                     5.2.1   Standards and Guidelines
                     5.2.2   Accessibility Testing
               5.3 Summary
               5.4 Keywords
               5.5 Self Assessment
               5.6 Review Questions

               5.7 Further Readings
               Objectives
               After studying this unit, you will be able to:

               •    Explain the need for configuration testing
               •    Explain the importance of graphical user interface testing
               Introduction

               Testing a system is meant to ensure an error-free, quality product. A system undergoes several tests
               before its launch. This chapter emphasizes on configuration testing and graphical user interface testing.
               Testing a system is a methodology, which involves both the hardware and the software components of
               the system. System testing falls under the scope of black box testing. Therefore, system testing does not
               require  a software tester to  have a thorough knowledge  about the internal design  and code of the
               software. It unravels the defects within the system and between the various links  in the code
               (assemblages).
               Under system testing, the system that is to be tested is configured in a controlled environment. Real life
               scenarios are simulated in the test environment. This type of testing is considered to be complete on two
               scenarios: First when the actual results and the expected results match, and second when the differences
               between the actual results and the expected results are well explained and accepted based on client
               input.
               Thus, system testing is considered to be a process of exploring the functionality of the system and
               identifying the faults within the system. The following example gives you a better idea about breaking
               the system.












                                        LOVELY PROFESSIONAL UNIVERSITY                           61
   63   64   65   66   67   68   69   70   71   72   73