1. CS 217 Software Verification and Validation Week 9, Summer 2014 Instructor: Dong Si http://www.cs.odu.edu/~dsi

2. REVIEW OF THE CLASS

3. What is (software) testing?

4. Softeware Testing – definition n The process consisting of all life cycle activities, concerned with planning, preparation and evaluation of software products and related work products to determine: –that they satisfy specified requirements, –to demonstrate that they are fit for purpose and –to detect defects 4

5. Validation & Verification n Validation : Have we built the right software? n i.e., do the requirements satisfy the customer? n (This is dynamic process for checking and testing the real product. Software validation always involves with executing the code) n Verification : Have we built the software right? n i.e., does it implement the requirements? n This is static method for verifying design, code. Software verification is human based checking of documents and files Introduction to Software Testing, Edition 2 (Ch 1) © Ammann & Offutt 5

6. Introduction to Software Testing, Edition 2 (Ch 1) © Ammann & Offutt 6 n Software Fault : A static defect in the software n Software Failure : External, incorrect behavior with respect to the requirements or other description of the expected behavior n Software Error : An incorrect internal state that is the manifestation/expression of some fault Faults in software are equivalent to design mistakes in hardware. Software does not degrade. Software Faults, Errors & Failures

7. Fault and Failure Example n The doctor tries to diagnose the root cause, the disease –Fault n A patient gives a doctor a list of symptoms –Failures n The doctor may look for anomalous internal conditions (high blood pressure, irregular heartbeat, bacteria in the blood stream) –Errors Introduction to Software Testing, Edition 2 (Ch 1) © Ammann & Offutt 7 Most medical problems result from external attacks (bacteria, viruses) or physical degradation as we age. They were there at the beginning and do not “appear” when a part wears out.

8. Sources of Problems n Requirements Definition: Erroneous, incomplete, inconsistent requirements. n Design: Fundamental design flaws in the software. n Implementation: Mistakes in chip fabrication, wiring, programming faults, malicious code. n Support Systems: Poor programming languages, faulty compilers and debuggers, misleading development tools.

9. Sources of Problems (Cont’d) n Inadequate Testing of Software: Incomplete testing, poor verification, mistakes in debugging. n Evolution: Sloppy redevelopment or maintenance, introduction of new flaws in attempts to fix old flaws, incremental escalation to inordinate complexity.

10. Summary: Why Do We Test Software ? Introduction to Software Testing, Edition 2 (Ch 1) © Ammann & Offutt 10 A tester’s goal is to eliminate faults as early as possible Improve quality Improve quality Reduce cost Reduce cost Preserve customer satisfaction Preserve customer satisfaction

11. Testing main principles

12. Testing Principles (1) n Testing can demonstrate only the presence of defects and not their absence –Testing can show that defects are present, but cannot prove that there are no defects. Testing reduces the probability of undiscovered defects remaining in the software but, even if no defects are found, it is not a proof of correctness. n Exhaustive testing is impossible –Exhaustive testing (all combinations of inputs and preconditions) is not feasible except for trivial cases. Instead of exhaustive testing, risk analysis and priorities should be used to focus testing efforts.

13. Testing Principles (2) n Early testing is important –Testing activities should start as early as possible in the software or system development life cycle and should be focused on defined objectives. n Defects are clustering –A small number of modules contain most of the defects discovered during pre-release testing, or are responsible for the most operational failures.

14. Testing Principles (3) n Testing is context dependent –Testing is done differently in different contexts. For example, military software is tested differently from an business site.

15. Software Testing Process 15 Unit test Integration test System test System engineering Software Design Code & Implementation V&V Targets

16. Software Development Lifecycles n Code and Fix n Waterfall n Cycle

17. BASIC OF LOGICS

18. Motivation n LOGIC enabled mathematicians to point out WHY a proof is wrong, or WHERE in the proof, the reasoning has been faulty. n Faults (bugs) have been detected in proofs (programs) n Is such a tool that by symbolizing arguments rather than writing them out in some natural language (which is fraught with ambiguity), checking the correctness of a proof becomes a much more viable task. 18

19. Introduction to Logic  CS areas where we use LOGIC  Architecture (logic gates)  Software Engineering (Validation & Verification)  Programming Languages (Semantics & Logic Programming)  AI (Automatic theorem proving)  Algorithms (Complexity)  Databases (SQL) 19

20. Fundamental of Logic  Declarative statements n Examples of declarative statements –“A is older than B” –“There is ice in the glass” –In CIS, describing the data (variables, functions, etc.) 20

21.  Propositions - a statement that is either true or false.  For every proposition p, either p is T or p is F  For every proposition p, it is not the case that p is both T and F 21

22. Fundamental of Logic n We not only want to specify such statements, but also want to check whether a given program or system fulfills specifications that user needs. (Validation) n We are interested in precise declarative statements about computer systems and programs. (Verification) 22

23. Propositional Logic: Basics n Propositional logic describes ways to combine some true statements to produce other true statements. n If it is proposed that `Jack is taller than John' and `John can run faster than Jack' are both T =`Jack is taller than John and John can run faster than Jack'. n Propositional logic allows us to formalize such statements. n In concise form: A ^ B 23

24. Propositional Logic n Composition of atomic sentences p: I won the lottery yesterday q: I will purchase a lottery ticket today r: I played a football game yesterday n ~ p: Negation. “I did not win the lottery last week” n p v r: Disjunction. The statement is true if at least one of them is true. “I won the lottery or played a football game yesterday.” 24

25. Propositional Logic n p ^ r: Conjunction. “Yesterday I won the lottery and played a football game.” n p q: Implication. “If I won the lottery last week, then I will purchase a lottery ticket today.” p is called the assumption and q is called conclusion. –p implies q –If p then q 25

26. Natural Deduction n Proof n Set of rules which allow us to draw a conclusion by given a set of preconditions n Constructing a proof is much like a programming! n It is not obvious which rules to apply and in what order to obtain the desired conclusion, be careful to choose proof rules! 26

27. Rules of Natural Deduction n Fundamental rule 1 (rule of detachment) p p q... q n The rule is a valid inference because [p ^ (p q)] q is a tautology! 27

28. Rules of Natural Deduction n Example: if it is 11:00 o’ clock in Norfolk if it is 11:00 o’ clock in Norfolk, then it is 11:00 o’ clock in DC then by rule of detachment, we must conclude: it is 11:00 o’ clock in DC 28

29. Rules of Natural Deduction n Fundamental rule 2 (transitive rule) p q q r... p r This is a valid rule of inference because the implication (p q) ^ (q r) (p r) is a tautology! 29

30. Rules of Natural Deduction n FR 3 (De Morgan’s law) ~(p v q) = (~p) ^ (~q) ~(p ^ q) = (~p) v (~q) n FR 4 (Law of contrapositive) p q = (~q ~p) n FR 5 (Double Negation) ~(~p) = p 30

31. Examples of Arguments n If a baby is hungry, then the baby cries. If the baby is not mad, then he does not cry. If a baby is mad, then he has a red face. Therefore, if a baby is hungry, then he has a red face. n Model this problem!! n h: a baby is hungry c: a baby cries m: a baby is mad r: a baby has a red face 31 h c ~m ~c m r... h r h c c m m r... h r

32. Logic is the Skeleton n What remains when arguments are symbolized is the bare logical skeleton n It is this form that enables us to analyze the program / code / software. n Software V&V = Logical proof & Logic error detection 32

33. n Q4. Problem: “Tom is a math major but not computer science major” M: Tom is a math major C: Tom is a computer science major n Tasks: Use De Morgan's Law to write the negation of the above statement as logic expression

34. n Answer: n Original: n M Λ ¬ C (Tom is a math major but not computer science major) n Negation: n ¬ (M Λ ¬ C) = ¬ M V ¬ (¬ C) (De Morgan's Laws) = ¬ M V C (Double negation rule) 34

35. BLACK-BOX TESTING & WHITE-BOX TESTING

36. Differences Between BB and WB 36

37. Black-Box Testing 37

38. White-Box testing 38

39. REVIEW OF BB-testing

40. Black-box Testing 1. Input Space Partitioning 2. Boundary Value Analysis 40

41. Example 1: compare two numbers – p50 of week3 n Function ‘Compare (x, y)’ n Inputs: Two numbers – x and y n Outputs: A larger number between x and y 41 Compare (x, y) = z (x, y) z

42. – p51 of week3 42 Equivalence Classes: { (x, y) | x < y } { (x, y) | x > y } { (x, y) | x = y } { input other than a pair of numbers, “as&%dfget^$(&w” } Valid inputs Invalid inputs

43. 43 Valid (x, y) Input Space x = y x < y x > y Three test cases: (1, 2) --- 2 (8, 8) --- 8 (100, 30) --- 100 Plus one test cases: (^&%*) --- ERROR – p52 of week3

44. Example 2: Loan application - p53 of week3 44 Customer Name Account number Loan amount requested Term of loan Monthly repayment Term: Repayment: Interest rate: Total paid back: 6 digits, 1st non-zero $500 to $9000 1 to 30 years Minimum $10 2-64 chars. Choosing (or defining) partitions seems easy, but is easy to get wrong…

45. 45 Customer name Number of characters: 26465 invalidvalidinvalid 1 Valid characters: Any other A-Z a-z -’ space

46. 46 Loan amount 50090009001 invalidvalidinvalid 499

47. WB Testing Techniques n Logic coverage: (learned in previous classes)  Statement coverage  Branch coverage  Condition coverage  … n Dataflow based testing / Path coverage: all program paths have been traversed at least once 47

48. Pseudo code & Control/Dataflow Graphs 48 “nodes” “edges” Input output Absolute (x) { IF (x>=0) THEN y = x; ELSE IF (x<0) THEN y = -x; Output y; } x IF (x>=0)ELSE IF (x<0) y = x; y = -x; y