Presentation is loading. Please wait.

Presentation is loading. Please wait.

WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.

Similar presentations


Presentation on theme: "WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010."— Presentation transcript:

1 WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010. They may not show up well on other PowerPoint versions. You can download PowerPoint 2010 viewer from here.here These slides contain a lot of animations. For optimal results, watch in slideshow mode. 30 min

2

3

4

5 But it worked in my machine! Our tester Your software

6 Quality Assurance: Testing and Beyond CS2103/T, Lecture 9, Part 1, [Oct 18, 2013]

7

8 ValidationVerification [Quality Assurance]

9 ValidationVerification [Quality Assurance] Are we building the correct product? Are we building the product correctly?

10 ValidationVerification [Quality Assurance] Are we building the correct product? Are we building the product correctly?

11 ValidationVerification [Quality Assurance] Are we building the correct product? Are we building the product correctly? FAIL!

12 ValidationVerification [Quality Assurance] Are we building the correct product? Are we building the product correctly? FAIL! FAIL!

13 ValidationVerification [Quality Assurance] Buggy requirements Buggy code FAIL! FAIL!

14 ValidationVerification [Quality Assurance] Two QA activities for a PC version of a ‘Snakes and ladders’ game: a) Ensure that the game allows players to decide who throws the die first. b) When more than one piece is on a square, ensure that it is the piece that belongs to the current player that will be moved. (Are we building the correct product?) (Are we building the product correctly?) snakes {a|b} e.g. snakes a snakes {a|b} e.g. snakes a 77577 tinyurl.com/questionSMS Which one is more related to verification than validation?

15 ValidationVerification [Quality Assurance]

16 ValidationVerification [Quality Assurance]

17 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance]

18 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance] Product

19 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance] Product

20 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance] Product

21 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance] Product But it worked in my machine!

22 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance] Product

23 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance] Product System specification Requirements specification

24 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance] Product System specification Requirements specification

25 ValidationVerification [Quality Assurance] Product E.g. Acceptance testingE.g. System testing

26 ValidationVerification [Quality Assurance] Product E.g. Acceptance testingE.g. System testing

27 ValidationVerification [Quality Assurance] Product E.g. Acceptance testingE.g. System testing

28 ValidationVerification E.g. Acceptance testingE.g. System testing Back-end GUI [Quality Assurance] Product

29 ValidationVerification E.g. Acceptance testingE.g. System testing Back-end GUI [Quality Assurance] GUI testing

30 ValidationVerification E.g. Acceptance testingE.g. System testing Back-end GUI [Quality Assurance] GUI testing

31 ValidationVerification E.g. Acceptance testingE.g. System testing Back-end GUI [Quality Assurance] GUI testing

32 ValidationVerification E.g. Acceptance testingE.g. System testing Back-end GUI [Quality Assurance] GUI testing GUI Logic Automated API tester Manual testing (or automate)

33 ValidationVerification E.g. Acceptance testingE.g. System testing Back-end GUI [Quality Assurance] GUI testing GUI Logic Automated API tester Manual testing (or automate)

34 ValidationVerification E.g. Acceptance testingE.g. System testing Back-end GUI [Quality Assurance] GUI testing

35

36

37

38

39

40

41 ValidationVerification E.g. Acceptance testingE.g. System testing Back-end GUI [Quality Assurance] GUI testing

42 ValidationVerification E.g. Acceptance testingE.g. System testing Back-end GUI [Quality Assurance]

43 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance] ← How much of this is being tested?

44 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance] ← How much of this is being tested?

45

46

47

48

49 Using EclEmma coverage tool on TEAMMATES

50 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance] ← How much of this is being tested?

51 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance] ← How much of this is being tested? Statement coverage Function coverage Condition coverage Exit/entry coverage Branch coverage Path coverage

52 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance] ← How much of this is being tested? Statement coverage Path coverage

53 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance] ← How much of this is being tested? Statement coverage Path coverage void readInput(){ while ( hasInput() ) input += readFromKeyboard(); }

54 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance] ← How much of this is being tested? Statement coverage void readInput(){ while ( hasInput() ) input += readFromKeyboard(); }

55 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance] ← How much of this is being tested? void readInput(){ while ( hasInput() ) input += readFromKeyboard(); } Path coverage

56 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance] ← How much of this is being tested? void readInput(){ while ( hasInput() ) input += readFromKeyboard(); } Path coverage

57 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance] ← How much of this is being tested? void readInput(){ while ( hasInput() ) input += readFromKeyboard(); } Path coverage

58 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance] ← How much of this is being tested? void readInput(){ while ( hasInput() ) input += readFromKeyboard(); } Path coverage

59 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance] ← How much of this is being tested? void readInput(){ while ( hasInput() ) input += readFromKeyboard(); } Path coverage

60 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance] ← How much of this is being tested? Path coverage void readInput(){ while ( hasInput() ) input += readFromKeyboard(); } Control Flow Graphs

61 ValidationVerification E.g. Acceptance testingE.g. System testing [Quality Assurance] ← How much of this is being tested? Statement coverage Function coverage Condition coverage Exit/entry coverage Branch coverage Path coverage

62 ValidationVerification E.g. Acceptance testing [Quality Assurance] E.g. System testing just testing?

63 ValidationVerification E.g. Acceptance testing [Quality Assurance] E.g. System testing Other QA techniques just testing?

64 [Quality Assurance] Other QA techniques

65 ValidationVerification E.g. Acceptance testing [Quality Assurance] Code reviews static analysis formal methods … Other QA techniques

66 ValidationVerification E.g. Acceptance testing [Quality Assurance] Other QA techniques Code reviews static analysis formal methods …

67 ValidationVerification E.g. Acceptance testing [Quality Assurance] Other QA techniques Code reviews static analysis formal methods …

68 ValidationVerification E.g. Acceptance testing [Quality Assurance] Other QA techniques Code reviews static analysis formal methods …

69 ValidationVerification E.g. Acceptance testing [Quality Assurance] Other QA techniques Code reviews static analysis formal methods …

70 ValidationVerification E.g. Acceptance testing [Quality Assurance] Other QA techniques Code reviews static analysis formal methods … Using CodeProAnalytix static analysis tool on TEAMMATES

71 ValidationVerification E.g. Acceptance testing [Quality Assurance] Other QA techniques Code reviews static analysis formal methods …

72 ValidationVerification E.g. Acceptance testing [Quality Assurance] Other QA techniques Code reviews static analysis formal methods … SUT doubleAmount(int):int SUT doubleAmount(int):int

73 ValidationVerification E.g. Acceptance testing [Quality Assurance] Other QA techniques Code reviews static analysis formal methods … Text case 1: Input: 23 Expected output: 46 Text case 2: Input: 10 Expected output : 20 Text case n: Input: -2 Expected output : -4 … Testing SUT doubleAmount(int):int SUT doubleAmount(int):int

74 ValidationVerification E.g. Acceptance testing [Quality Assurance] Other QA techniques Code reviews static analysis formal methods … Mathematically prove if input = x then, output = 2x Testing SUT doubleAmount(int):int SUT doubleAmount(int):int Text case 1: Input: 23 Expected output: 46 Text case 2: Input: 10 Expected output : 20 Text case n: Input: -2 Expected output : -4 …

75 ValidationVerification E.g. Acceptance testing [Quality Assurance] Other QA techniques Code reviews static analysis formal methods …

76 ValidationVerification E.g. Acceptance testing [Quality Assurance] Other QA techniques Code reviews static analysis formal methods …

77

78 Have the ability to relate these concepts to the project: validation, verification, system testing, acceptance testing, code coverage, GUI testing, other QA techniques. For example, the ability to explain how the above was done in the project, or why they were not done and how you could have done them. You are welcome to, but not required to, use Automation of GUI testing Using tools to measure coverage Path analysis Apply other QA techniques

79 If all tests pass and those tests achieve100% path coverage (all possible execution paths through the code have been tested), can the software still have bugs? (Discuss with neighbors before submitting) buggy {yes|no} e.g. buggy yes buggy {yes|no} e.g. buggy yes 77577 tinyurl.com/questionSMS


Download ppt "WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010."

Similar presentations


Ads by Google