Page 162 - SOFTWARE TESTING & QUALITY ASSURANCE
P. 162

Pawan Kumar, Lovely Professional University                  Unit 11: Test Case Planning




                                       Unit 11: Test Case Planning



               CONTENTS
                Objectives
               Introduction
               11.1 Test Cases

                    11.1.1   Test Case Planning
                    11.1.2   Test Design
                    11.1.3   Writing Test Cases
                    11.1.4   Test Procedures
                    11.1.5   Test Organization and Tracking
               11.2 Bug’s Life Cycle
                    11.2.1    Stages of a Bug
                       11.2.2   Bug Tracking System

               11.3 Summary
               11.4 Keywords
               11.5 Self Assessment
               11.6 Review Questions

               11.7 Further Readings
               Objectives

               After studying this unit, you will be able to:
               •    Explain the test case design procedure
               •    Analyze bug life cycle

               Introduction
               We are aware that test cases are pivotal to any Test Plan. They help us discover information about the
               product. According to  IEEE Standard  610  Test  cases are defined  as  “A set of test inputs, execution
               conditions, and expected results developed for a particular objective, such as to exercise a particular
               program path or to verify compliance  with a specific requirement.” Another  definition from  IEEE
               Standard 829 states that test cases are “Documentation specifying inputs, predicted results, and a set of
               execution conditions for a test item.”
               Let us now learn the different definitions of test cases. According to Ron Patton, “Test cases are the
               specific inputs that you’ll try and the procedures that you’ll follow when you test the software.” Boris
               Beizer  defines a test as  “A sequence of one or more subtests executed as a sequence because the
               outcome and/or final state of one subtest is the input and/or initial state of the next.” The word ‘test’ is
               used to include subtests, tests proper, and test suites.
               Perhaps, a simpler definition is stated by Brian Marick, who calls the test case as test idea, where he
               defines as follows, “A test idea is a brief statement of something that should be tested. For example, if
               you're testing a square root function, one idea for a test would be ‘test a number less than zero’. The
               idea is to check if the code handles an error case.”






                                        LOVELY PROFESSIONAL UNIVERSITY                          155
   157   158   159   160   161   162   163   164   165   166   167