Types of TestingSlide 2Slide 3Unit TestingIntegration TestingSystem TestingVolume TestingStress TestingRecovery TestingAcceptance TestingPowerPoint PresentationSoftware Testing IssuesAlpha/Beta TestingTest ScriptsSlide 15Registration Example Test ScriptsTypes of Testing•Inspection–Formal group activities where participants manually examine code for occurrences of well-known errors, syntax, logic•Where is the read next record•Dates•Negative Logic–Function of the code is not testedTypes of Testing•Walkthroughs–Manual check of the function of code –“Random” group of programmers•Who selects the programmers•Should the BOSS be at the walk through–Checks consistency of code with coding standards–When•Before computer testing•After computer testingTypes of Testing•Automated–Unit–Integration–System–Volume–AcceptanceUnit Testing•Each module is tested alone in an attempt to discover any errors in its code•Test each line of codeIntegration Testing•The process of bringing together all of the modules that a program comprises for testing purposes.•Modules are typically integrated in a top-down incremental fashionSystem Testing•Bringing together of all of the programs that a system comprises for testing purposes in a top down fashion•Start with the control module•Stub testing–Substitute generic code to test the lowest level modulesVolume Testing•Increase size of file•Increase number of users•Impact on storage/response issuesStress Testing•Tries to break the hardware system.•Impact on other systems•Problems with concurrent usersRecovery Testing•Can a corrupt file be recreated?–Amount of lost data•Backing up of data–Full versus Incremental –Timing–How long/how many of the backups should be saved?Acceptance Testing•The process whereby actual users test a completed information systemSoftware Testing MethodologyUser Acceptance TestingVolume/Stress/Recovery TestingSystem TestingIntegration TestingUnit TestingSoftware Testing Issues•Who should do the testing–programmers–professional tester–the end user•Testing Strategies:–Top-Down–Bottom-Up–Black box–White box–Alpha–BetaAlpha/Beta Testing•Alpha Testing–Using simulation data•Beta testing–Using real data–Done by user in the user environmentTest Scripts•Using simulation data•Create a test case to ensure that each line of code will be tested•Registration example–Invalid Social Security Number–Attempt to add a class with an invalid call number–Attempt to add a closed class–Invalid SSN (not a student)–Register for two classes at the same time–Register before you have the required cumulative hoursTest Scripts•Identify test case•Specify in detail desired outcomes of test case•Specify in detail actual outcomes of test case•Resolve discrepancies, if any–Who should do this?–To whom should the discrepancy be reported?•Log the resultsRegistration ExampleTest Scripts•What would happen IF–A valid SSN was keyed - but the student has no classes on the student class table–An invalid SSN was keyed –A valid SSN was keyed and •The student has 4 classes•The student has 7 classes•The student has 10
View Full Document
Unlocking...