1. Hello
My Name is
Software Testing
Thursday, October 18, 12

2. Who am I?
Prathan Dansakulcharoenkit
Scrum Master + CBO + ITIL Coach @ OpenDream
Consult Manager @ FedilityQA
Outsource Project Manager @ TARAD Dot Com
IT Development Manager @ TARAD Dot Com
Assistance Services & Operation Manager @ Sanook.com
QA Specialist @ Sanook.com
Tester @ Sanook.com
System Administrator @ POPidols.net
Freelance Programmer
Thursday, October 18, 12

3. UNLEARN
Thursday, October 18, 12

4. Software Quality
Thursday, October 18, 12

5. Quality Triangle
Thursday, October 18, 12

6. Quality Triangle
Thursday, October 18, 12

7. Quality Triangle
Requirements
Thursday, October 18, 12

8. Quality Triangle
Requirements Specification
Thursday, October 18, 12

9. Quality Triangle
Software
Requirements Specification
Thursday, October 18, 12

10. Quality Triangle
Software
Gap
Requirements Specification
Thursday, October 18, 12

11. Quality Triangle
Software
Gap
Requirements
Thursday, October 18, 12

12. Quality Triangle
Software
Gap
Thursday, October 18, 12

13. Quality Triangle
Gap
Thursday, October 18, 12

14. Quality Triangle
Thursday, October 18, 12

15. Quality Triangle
Thursday, October 18, 12

16. Quality Triangle
Thursday, October 18, 12

17. Quality Triangle
Thursday, October 18, 12

18. Quality Triangle
Thursday, October 18, 12

19. Quality Triangle
Thursday, October 18, 12

20. Quality Triangle
Thursday, October 18, 12

21. Quality Triangle
Requirements
Thursday, October 18, 12

22. Quality Triangle
Specification
Requirements
Thursday, October 18, 12

23. Quality Triangle
Software
Specification
Requirements
Thursday, October 18, 12

24. Quality Triangle
Software
Specification
Requirements
It’s an IDEAL!!!
Thursday, October 18, 12

25. Quality Triangle
Thursday, October 18, 12

26. Quality Triangle
In the real WORLD
Thursday, October 18, 12

27. Quality Triangle
Software
Requirements Specification
In the real WORLD
Thursday, October 18, 12

28. Quality Triangle
Software
Requirements Specification
In the real WORLD
Thursday, October 18, 12

29. Quality Triangle
Software
Software
Requirements Specification
Requirements Specification
In the real WORLD
Thursday, October 18, 12

30. Quality Triangle
Software
Software
Requirements Specification
Requirements Specification
In the real WORLD
Thursday, October 18, 12

31. Quality Triangle
Software
Software Software
Requirements Specification
Specification
Requirements Specification
In the real WORLD
Thursday, October 18, 12

32. Quality Triangle
Software
Software Software
Requirements Specification
Specification
Requirements Specification
In the real WORLD
Thursday, October 18, 12

33. Quality Triangle
Software
Software
Software Software
Requirements Specification
Specification
Requirements
Requirements SpecificationSpecification
In the real WORLD
Thursday, October 18, 12

34. Quality Triangle
Software
Software
Software Software
Requirements Specification
Specification
Requirements
Requirements SpecificationSpecification
In the real WORLD
Thursday, October 18, 12

35. Quality Triangle
Software
Software
Software Software
Software
Requirements Specification
Specification
Specification
Requirements
Requirements
Requirements SpecificationSpecification
In the real WORLD
Thursday, October 18, 12

36. Software Testing
Thursday, October 18, 12

37. Where Do bug Come?
Thursday, October 18, 12

38. Where Do bug Come?
Requirements definition
Thursday, October 18, 12

39. Where Do bug Come?
Requirements definition
System design
Thursday, October 18, 12

40. Where Do bug Come?
Requirements definition
System design
Implementation
Thursday, October 18, 12

41. Where Do bug Come?
Requirements definition
System design
Implementation
Support systems
Thursday, October 18, 12

42. Where Do bug Come?
Requirements definition
System design
Implementation
Support systems
Inadequate testing of Software
Thursday, October 18, 12

43. Where Do bug Come?
Requirements definition
System design
Implementation
Support systems
Inadequate testing of Software
Evolution
Thursday, October 18, 12

44. Cost of Bug
Thursday, October 18, 12

45. Cost of Bug
Tester use 10 minutes to record 1 bug
Thursday, October 18, 12

46. Cost of Bug
Tester use 10 minutes to record 1 bug
350 bugs is used 3,500 minutes = 58 hours
Thursday, October 18, 12

47. Cost of Bug
Tester use 10 minutes to record 1 bug
350 bugs is used 3,500 minutes = 58 hours
Developer use 3 minutes to feedback 1 bug
Thursday, October 18, 12

48. Cost of Bug
Tester use 10 minutes to record 1 bug
350 bugs is used 3,500 minutes = 58 hours
Developer use 3 minutes to feedback 1 bug
350 bugs is used 1,050 minutes = 17 hours
Thursday, October 18, 12

49. Cost of Bug
Tester use 10 minutes to record 1 bug
350 bugs is used 3,500 minutes = 58 hours
Developer use 3 minutes to feedback 1 bug
350 bugs is used 1,050 minutes = 17 hours
Tester use 3 minutes to change status of 1 bug
Thursday, October 18, 12

50. Cost of Bug
Tester use 10 minutes to record 1 bug
350 bugs is used 3,500 minutes = 58 hours
Developer use 3 minutes to feedback 1 bug
350 bugs is used 1,050 minutes = 17 hours
Tester use 3 minutes to change status of 1 bug
350 bugs is used 1,050 minutes = 17 hours
Thursday, October 18, 12

51. Cost of Bug
Tester use 10 minutes to record 1 bug
350 bugs is used 3,500 minutes = 58 hours
Developer use 3 minutes to feedback 1 bug
350 bugs is used 1,050 minutes = 17 hours
Tester use 3 minutes to change status of 1 bug
350 bugs is used 1,050 minutes = 17 hours
Thursday, October 18, 12

52. Cost of Bug
Tester use 10 minutes to record 1 bug
350 bugs is used 3,500 minutes = 58 hours
Developer use 3 minutes to feedback 1 bug
350 bugs is used 1,050 minutes = 17 hours
Tester use 3 minutes to change status of 1 bug
350 bugs is used 1,050 minutes = 17 hours
Thursday, October 18, 12

53. Cost of Bug
Tester use 10 minutes to record 1 bug
350 bugs is used 3,500 minutes = 58 hours
Developer use 3 minutes to feedback 1 bug
350 bugs is used 1,050 minutes = 17 hours
Tester use 3 minutes to change status of 1 bug
350 bugs is used 1,050 minutes = 17 hours
Thursday, October 18, 12

54. Cost of Bug
Tester use 10 minutes to record 1 bug
350 bugs is used 3,500 minutes = 58 hours
Developer use 3 minutes to feedback 1 bug
350 bugs is used 1,050 minutes = 17 hours
Tester use 3 minutes to change status of 1 bug
350 bugs is used 1,050 minutes = 17 hours
Thursday, October 18, 12

55. Cost of Bug
Tester use 10 minutes to record 1 bug
350 bugs is used 3,500 minutes = 58 hours
Developer use 3 minutes to feedback 1 bug
350 bugs is used 1,050 minutes = 17 hours
Tester use 3 minutes to change status of 1 bug
350 bugs is used 1,050 minutes = 17 hours
Thursday, October 18, 12

56. Cost of Bug
Tester use 10 minutes to record 1 bug
350 bugs is used 3,500 minutes = 58 hours
Developer use 3 minutes to feedback 1 bug
350 bugs is used 1,050 minutes = 17 hours
Tester use 3 minutes to change status of 1 bug
350 bugs is used 1,050 minutes = 17 hours
Thursday, October 18, 12

57. Cost of Bug
Tester use 10 minutes to record 1 bug
350 bugs is used 3,500 minutes = 58 hours
58 hrs + 17minutes+to17 hrs = bug hr
Developer use 3 hrs feedback 1 92
350 bugs is used 1,050 minutes = 17 hours
Tester use 3 minutes to change status of 1 bug
350 bugs is used 1,050 minutes = 17 hours
Thursday, October 18, 12

58. Cost of Bug
Tester use 10 minutes to record 1 bug
350 bugs is used 3,500 minutes = 58 hours
58 hrs + 17minutes+to17 hrs = bug hr
Developer use 3 hrs feedback 1 92
350 bugs is used 1,050 minutes = 17 hours
4 days
Tester use 3 minutes to change status of 1 bug
350 bugs is used 1,050 minutes = 17 hours
Thursday, October 18, 12

59. What do you think
software testing is?
Thursday, October 18, 12

60. Some Facts of Testing
Thursday, October 18, 12

61. Some Facts of Testing
ALWAYS be a chance that software will have bugs
Thursday, October 18, 12

62. Some Facts of Testing
ALWAYS be a chance that software will have bugs
CANNOT prove software works by testing it
Thursday, October 18, 12

63. Some Facts of Testing
ALWAYS be a chance that software will have bugs
CANNOT prove software works by testing it
DOES NOT prove that software is bug-free
Thursday, October 18, 12

64. Some Facts of Testing
ALWAYS be a chance that software will have bugs
CANNOT prove software works by testing it
DOES NOT prove that software is bug-free
Testing after software has been created DOES NOT
improve its quality
Thursday, October 18, 12

65. Some Facts of Testing
ALWAYS be a chance that software will have bugs
CANNOT prove software works by testing it
DOES NOT prove that software is bug-free
Testing after software has been created DOES NOT
improve its quality
Cost of removing bugs rises DRAMATICALLY in the
later phases of the software development process
Thursday, October 18, 12

66. Some Facts of Testing
ALWAYS be a chance that software will have bugs
CANNOT prove software works by testing it
DOES NOT prove that software is bug-free
Testing after software has been created DOES NOT
improve its quality
Cost of removing bugs rises DRAMATICALLY in the
later phases of the software development process
QUALITY depends on 3 factors; People, Process
and Tool
Thursday, October 18, 12

67. Some Facts of Testing
ALWAYS be a chance that software will have bugs
CANNOT prove software works by testing it
DOES NOT prove that software is bug-free
Testing after software has been created DOES NOT
improve its quality
Cost of removing bugs rises DRAMATICALLY in the
later phases of the software development process
QUALITY depends on 3 factors; People, Process
and Tool
Thursday, October 18, 12

68. Some Facts in NASA
as the 120-tons space shuttle sits surrounded by almost 4
million pounds of rocket fuel..
...the last three versions of the program -- each 420,000
lines long-had just one error each. The last 11
versions of this software had a total of 17 errors...
Source: http://www.fastcompany.com/magazine/06/writestuff.html
Thursday, October 18, 12

69. Some Facts in NASA
Thursday, October 18, 12

70. Some Goals of Testing
Thursday, October 18, 12

71. Some Goals of Testing
Determine a product MEET business expectation
Thursday, October 18, 12

72. Some Goals of Testing
Determine a product MEET business expectation
MINIMIZE the risk of error occurs
Thursday, October 18, 12

73. Some Goals of Testing
Determine a product MEET business expectation
MINIMIZE the risk of error occurs
IS NOT the process to verify software work correct
Thursday, October 18, 12

74. Some Goals of Testing
Determine a product MEET business expectation
MINIMIZE the risk of error occurs
IS NOT the process to verify software work correct
Testing must be to DEMONSTRATE that software
does have bug
Thursday, October 18, 12

75. Some Goals of Testing
Determine a product MEET business expectation
MINIMIZE the risk of error occurs
IS NOT the process to verify software work correct
Testing must be to DEMONSTRATE that software
does have bug
Tester must find bug as EARLY as possible and
make sure that they are fixed
Thursday, October 18, 12

76. What are testing types you
know?
Thursday, October 18, 12

77. Testing Types
Thursday, October 18, 12

78. Testing Types
Unit testing
Thursday, October 18, 12

79. Testing Types
Unit testing
Integration testing
Thursday, October 18, 12

80. Testing Types
Unit testing
Integration testing
System testing
Thursday, October 18, 12

81. Testing Types
Unit testing
Integration testing
System testing
User Acceptance testing
Thursday, October 18, 12

82. Testing Types
Unit testing
Integration testing
System testing
User Acceptance testing
Regression testing
Thursday, October 18, 12

83. Testing Types
Unit testing
Integration testing
System testing
User Acceptance testing
Regression testing
Performance testing
Thursday, October 18, 12

84. Testing Types
Unit testing
Integration testing
System testing
User Acceptance testing
Regression testing
Performance testing
Security testing
Thursday, October 18, 12

85. Testing Types
Unit testing
Integration testing
System testing
User Acceptance testing
Regression testing
Performance testing
Security testing
Usability testing
Thursday, October 18, 12

86. Testing Types
Unit testing
Integration testing
System testing
User Acceptance testing
Regression testing
Performance testing
Security testing
Usability testing
Compatibility testing
Thursday, October 18, 12

87. Testing Types
A
C
B
D
E
F G
Thursday, October 18, 12

88. Testing Types
A
C
B
D Module
E
F G
Thursday, October 18, 12

89. Testing Types
Integrate A
C
B
D Module
E
F G
Thursday, October 18, 12

90. Testing Types
Integrate A
C
B
D Module
E
F G
System
Thursday, October 18, 12

91. Testing Types
Thursday, October 18, 12

92. Test Case
Thursday, October 18, 12

93. Test Case
inputs to test system and verify
with expected outputs
Thursday, October 18, 12

94. Test Case
inputs to test system and verify
with expected outputs
Test Case = Test Rule + Test Data
Thursday, October 18, 12

95. Test Iterations
Thursday, October 18, 12

96. Test Iterations
Test to Pass
Thursday, October 18, 12

97. Test Iterations
Test to Pass
Test to Fail
Thursday, October 18, 12

98. Test Iterations
Test to Pass
Test to Fail
Thursday, October 18, 12

99. Who feel responsible for
QUALITY in traditional
development (Waterfell)?
Thursday, October 18, 12

100. Who feel responsible for
QUALITY in traditional
development (Waterfell)?
SOMEONE
Thursday, October 18, 12

101. Who feel responsible for
QUALITY in traditional
development (Waterfell)?
Thursday, October 18, 12

102. Who feel responsible for
QUALITY in traditional
development (Waterfell)?
WHOLE TEAM
Thursday, October 18, 12

103. Whole Team Approach
Thursday, October 18, 12

104. Whole Team Approach
Team commitment to quality
Thursday, October 18, 12

105. Whole Team Approach
Team commitment to quality
Team responsible for testing
Thursday, October 18, 12

106. Whole Team Approach
Team commitment to quality
Team responsible for testing
Tester get support, training
Thursday, October 18, 12

107. Whole Team Approach
Team commitment to quality
Team responsible for testing
Tester get support, training
Developers doing testing activities
Thursday, October 18, 12

108. Whole Team Approach
Team commitment to quality
Team responsible for testing
Tester get support, training
Developers doing testing activities
Tester and developer pair
Thursday, October 18, 12

109. Whole Team Approach
Team commitment to quality
Team responsible for testing
Tester get support, training
Developers doing testing activities
Tester and developer pair
Get the right person
Thursday, October 18, 12

110. Team Organization
Traditional Organization
xA
Tester
Dev
Thursday, October 18, 12

111. Team Organization
Agile Organization
Domain
Expert
Dev
Tester
Thursday, October 18, 12

112. 3Cs
Card
Conversation
Confirmation
Thursday, October 18, 12

113. Test INFECTED
Thursday, October 18, 12

114. Quality Improvement by
found defect EARLY
Thursday, October 18, 12

115. Automate Testing in the
RIGHT time
Thursday, October 18, 12

116. Don’t tell your team,
WE DO AGILE
Thursday, October 18, 12

117. Process’n Clock
Thursday, October 18, 12

118. We don’t build the software
We make it work with
QUALITY
Thursday, October 18, 12

119. Quality in every phase,
Not afterthought
Thursday, October 18, 12

120. Keep in touch
email: zyracuze@gmail.com
twitter: @zyracuze
facebook: zyracuze
blog: www.welovebug.com
Thursday, October 18, 12

121. Thanks You
Thursday, October 18, 12