Types 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 tested
Types 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 testing
Types of Testing
• Automated
– Unit
– Integration
– System
– Volume
– Acceptance
Unit Testing
• Each module is tested alone in an attempt to
discover any errors in its code
• Test each line of code
Integration 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 fashion
System 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
modules
Volume Testing
• Increase size of file
• Increase number of users
• Impact on storage/response issues
Stress Testing
• Tries to break the hardware system.
• Impact on other systems
• Problems with concurrent users
Recovery 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 system
Software Testing
Methodology
User Acceptance Testing
Volume/Stress/Recovery Testing
System Testing
Integration Testing
Unit Testing
Software Testing Issues
• Who should do the testing
– programmers
– professional tester
– the end user
• Testing Strategies:
– Top-Down
– Bottom-Up
– Black box
– White box
– Alpha
– Beta
Alpha/Beta Testing
• Alpha Testing
– Using simulation data
• Beta testing
– Using real data
– Done by user in the user environment
Test 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 hours
Test 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 results
Registration Example
Test 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 classes