1. technology and computing
2. software
3. databases

Transcribed Notes Lecture 2 Part 1: (First 40 minutes)
00:00:00 Subject: Class Detail


Exam grade is coming soon.
HW 2 is coming soon
00:01:07 Subject: Testing in General
00:01:17 Subject: Test Case


Test case is that when execute the software check if it gives the expect output for certain input
Example: Webreg
o Input:
 adding or dropping
 course code
 grade option
 student information
 student id
 student previous courses
 major
 units per quarter
 course prerequisite
o Output
 list of class enrolled
 update internal database about classes
 some output is not visible to student
00:07:35 Subject: Test Case Selection


Goals for selecting test cases (see overheads for slide)
o the relationship of confidence in module being tested and numbers of well selected or
not well selected test case with correct outputs
Quality of test cases (see overheads for slide)
o detect defects
 defect is bug in code comparing with error or failure
o detect location of the defect
o other qualities
 accurate
 whether the system gives correct output for input
o a story of professor in 1983
 he argue with a guy who test professor's code with the
wrong expected output and professor wins at the end
 thoroughness


 thoroughness means a reasonable search not necessary exhaust search
 test case show the present of bugs but not their absent
repeatable
 testing condition should be repeatable
 testing should not damage the system
systematic
 a systematic way to come up with test case is a better way
 in HW 2, related question will be asked
00:20:13 Subject: Levels and Types of Testing





unit testing
o it means test in small scale for basic function of the code
integration testing
o test if codes from two different group work together
 example: mars explore failure (imperial and matrix system)
acceptance testing
o usually done by custom to see if the software gives correct output
stress testing
o test if the system's capacity at a stressful scale
regression testing
o each time new feature is added, old test case need to be test again
00:28:39 Subject: A Quick Review




testing is required for quality insurance
test case need to be developed for testing
well selected test case need to be selected
what is the systematic approach to well selected test case?
00:29:48 Subject: Black Box and White Box Testing


black box testing
o do not look at the source code
o look at the requirements
o its thoroughness means
 has test case for each function
 handle all the variance of input
white box testing
o look at the source code
o test each line of code
o its thoroughness means
 a example (see overheads)


code coverage
 whether it runs each line of the code
branch coverage