A Review of Software Testing - P David Coward Reprinted: Information and Software Technology; Vol. 30, No. 3 April 1988Aim of paperNeedsSlide 4Slide 5TerminologySlide 7Categories of TestingFunctional TestingSlide 10Non-functional RequirementsSituation testingSlide 13QuestionsTesting StrategiesStrategy starting pointsSlide 17Functional testingSlide 19Slide 20Slide 21Structural testingSlide 23Slide 24Slide 25Slide 26Slide 27Slide 28Slide 29Slide 30Static analysisSlide 32Dynamic analysisSlide 34Classification of TechniquesSlide 36Slide 37Slide 38Symbolic executionSlide 40Slide 41Partition analysisSlide 43Program provingSlide 45Slide 46Slide 47Slide 48Anomaly analysisSlide 50Slide 51Slide 52Domain testingRandom testingSlide 55Adaptive perturbation testingSlide 57Cause-effect graphingSlide 59Slide 60Domain and computational testingSlide 62Slide 63Automatic test data generationMutation analysisSlide 66Slide 67ConclusionA Review of Software TestingA Review of Software Testing- P David Coward- P David CowardReprinted: Information and Software Reprinted: Information and Software Technology; Vol. 30, No. 3 April 1988Technology; Vol. 30, No. 3 April 1988Software Engineering: The Software Engineering: The Development Process, Vol 1,Development Process, Vol 1,Chapter 7Chapter 7Presented By: Andrew DiemerPresented By: Andrew DiemerSoftware Engineering II – EEL 6883Software Engineering II – EEL 6883Aim of paperAim of paper No guarantee that software meets No guarantee that software meets functional requirementsfunctional requirements Introduces software testing Introduces software testing techniquestechniquesNeedsNeeds Software is to be correctSoftware is to be correct– What does this meanWhat does this mean It often means the program It often means the program matches the specifications.matches the specifications. Problem with specificationProblem with specification– Specification could be wrongSpecification could be wrongNeedsNeeds If this happens then the If this happens then the correctness is measured by the correctness is measured by the software meeting the user software meeting the user requirementsrequirementsNeedsNeeds TestingTesting– Why testWhy test Tests may have not been Tests may have not been adequate enoughadequate enough Asses the performance of the Asses the performance of the taskstasksTerminologyTerminology Verification –vs- Validation Verification –vs- Validation  VerificationVerification– Ensures correctness from phase Ensures correctness from phase to phase of the software life cycle to phase of the software life cycle processprocess– Formal proofs of correctnessFormal proofs of correctnessTerminologyTerminology ValidationValidation– Checks software against Checks software against requirementsrequirements Executes software with test dataExecutes software with test data Author uses testing and checking Author uses testing and checking instead of verification and validationinstead of verification and validationCategories of TestingCategories of Testing Two categories of testing:Two categories of testing:– FunctionalFunctional– Non-functionalNon-functionalFunctional TestingFunctional Testing FunctionalFunctional– Addresses to see if the program Addresses to see if the program obtains the correct outputobtains the correct output It is normally used when testing a It is normally used when testing a modified or new programmodified or new programFunctional TestingFunctional Testing Regression TestingRegression Testing– Tests following modificationTests following modification– Tests to see if the unchanging Tests to see if the unchanging functions have indeed changedfunctions have indeed changedNon-functional RequirementsNon-functional Requirements StyleStyle Documentation standardsDocumentation standards Response timesResponse times Legal obligationsLegal obligationsSituation testingSituation testing Two situations testing can fall Two situations testing can fall under:under:– Testing which finds faults in the Testing which finds faults in the softwaresoftware– Testing which does NOT find Testing which does NOT find faults in the softwarefaults in the softwareSituation testingSituation testing Finding faultsFinding faults– Destructive processDestructive process more probingmore probing Not finding faultsNot finding faults– miss inherent faultsmiss inherent faults too gentletoo gentleQuestionsQuestions How much testing is needed?How much testing is needed? Confidence in testing?Confidence in testing? Ignore faults?Ignore faults?– Which ones are important?Which ones are important? Are there more faults?Are there more faults? What is the purpose of this What is the purpose of this testing?testing?Testing StrategiesTesting Strategies Functional -vs- StructuralFunctional -vs- Structural Static -vs- Dynamic analysisStatic -vs- Dynamic analysisStrategy starting pointsStrategy starting points SpecificationSpecification– It makes known the required It makes known the required functionsfunctions– Asses to see if they are providedAsses to see if they are provided– Functional testingFunctional testingStrategy starting pointsStrategy starting points SoftwareSoftware– Tests the structure of the systemTests the structure of the system– Structural testingStructural testing– Functions are included into the Functions are included into the system but are NOT requiredsystem but are NOT required– Example: accessing a database Example: accessing a database that has not been asked by the userthat has not been asked by the userFunctional testingFunctional testing Identify the functions which the Identify the functions which the software is expected to performsoftware is expected to perform Creating test data that will check Creating test data that will check to see if these functions are to see if these functions are performed by the softwareperformed by the software Does NOT matter how the Does NOT matter how the program performs these functionsprogram performs these functionsFunctional testingFunctional testing Rules may be applied to uncover Rules may be applied to uncover the functionsthe functions Functional testing methods of Functional testing methods of formal documentation that includes formal documentation that includes descriptions of faults that