Your SlideShare is downloading. ×
0
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
hello-my-name-is-software-testing-v2-pdf
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

hello-my-name-is-software-testing-v2-pdf

1,104

Published on

1 Comment
2 Likes
Statistics
Notes
No Downloads
Views
Total Views
1,104
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
32
Comments
1
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  1. Hello My Name is Software TestingThursday, 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 ProgrammerThursday, October 18, 12
  3. UNLEARNThursday, October 18, 12
  4. Software QualityThursday, October 18, 12
  5. Quality TriangleThursday, October 18, 12
  6. Quality TriangleThursday, October 18, 12
  7. Quality Triangle RequirementsThursday, October 18, 12
  8. Quality Triangle Requirements SpecificationThursday, October 18, 12
  9. Quality Triangle Software Requirements SpecificationThursday, October 18, 12
  10. Quality Triangle Software Gap Requirements SpecificationThursday, October 18, 12
  11. Quality Triangle Software Gap RequirementsThursday, October 18, 12
  12. Quality Triangle Software GapThursday, October 18, 12
  13. Quality Triangle GapThursday, October 18, 12
  14. Quality TriangleThursday, October 18, 12
  15. Quality TriangleThursday, October 18, 12
  16. Quality TriangleThursday, October 18, 12
  17. Quality TriangleThursday, October 18, 12
  18. Quality TriangleThursday, October 18, 12
  19. Quality TriangleThursday, October 18, 12
  20. Quality TriangleThursday, October 18, 12
  21. Quality Triangle RequirementsThursday, October 18, 12
  22. Quality Triangle Specification RequirementsThursday, October 18, 12
  23. Quality Triangle Software Specification RequirementsThursday, October 18, 12
  24. Quality Triangle Software Specification Requirements It’s an IDEAL!!!Thursday, October 18, 12
  25. Quality TriangleThursday, October 18, 12
  26. Quality Triangle In the real WORLDThursday, October 18, 12
  27. Quality Triangle Software Requirements Specification In the real WORLDThursday, October 18, 12
  28. Quality Triangle Software Requirements Specification In the real WORLDThursday, October 18, 12
  29. Quality Triangle Software Software Requirements Specification Requirements Specification In the real WORLDThursday, October 18, 12
  30. Quality Triangle Software Software Requirements Specification Requirements Specification In the real WORLDThursday, October 18, 12
  31. Quality Triangle Software Software Software Requirements Specification Specification Requirements Specification In the real WORLDThursday, October 18, 12
  32. Quality Triangle Software Software Software Requirements Specification Specification Requirements Specification In the real WORLDThursday, October 18, 12
  33. Quality Triangle Software Software Software Software Requirements Specification Specification Requirements Requirements SpecificationSpecification In the real WORLDThursday, October 18, 12
  34. Quality Triangle Software Software Software Software Requirements Specification Specification Requirements Requirements SpecificationSpecification In the real WORLDThursday, October 18, 12
  35. Quality Triangle Software Software Software Software Software Requirements Specification Specification Specification Requirements Requirements Requirements SpecificationSpecification In the real WORLDThursday, October 18, 12
  36. Software TestingThursday, October 18, 12
  37. Where Do bug Come?Thursday, October 18, 12
  38. Where Do bug Come? Requirements definitionThursday, October 18, 12
  39. Where Do bug Come? Requirements definition System designThursday, October 18, 12
  40. Where Do bug Come? Requirements definition System design ImplementationThursday, October 18, 12
  41. Where Do bug Come? Requirements definition System design Implementation Support systemsThursday, October 18, 12
  42. Where Do bug Come? Requirements definition System design Implementation Support systems Inadequate testing of SoftwareThursday, October 18, 12
  43. Where Do bug Come? Requirements definition System design Implementation Support systems Inadequate testing of Software EvolutionThursday, October 18, 12
  44. Cost of BugThursday, October 18, 12
  45. Cost of Bug Tester use 10 minutes to record 1 bugThursday, October 18, 12
  46. Cost of Bug Tester use 10 minutes to record 1 bug 350 bugs is used 3,500 minutes = 58 hoursThursday, 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 bugThursday, 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 hoursThursday, 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 bugThursday, 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 hoursThursday, 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 hoursThursday, 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 hoursThursday, 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 hoursThursday, 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 hoursThursday, 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 hoursThursday, 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 hoursThursday, 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 hoursThursday, 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 hoursThursday, October 18, 12
  59. What do you think software testing is?Thursday, October 18, 12
  60. Some Facts of TestingThursday, October 18, 12
  61. Some Facts of Testing ALWAYS be a chance that software will have bugsThursday, October 18, 12
  62. Some Facts of Testing ALWAYS be a chance that software will have bugs CANNOT prove software works by testing itThursday, 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-freeThursday, 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 qualityThursday, 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 processThursday, 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 ToolThursday, 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 ToolThursday, 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.htmlThursday, October 18, 12
  69. Some Facts in NASAThursday, October 18, 12
  70. Some Goals of TestingThursday, October 18, 12
  71. Some Goals of Testing Determine a product MEET business expectationThursday, October 18, 12
  72. Some Goals of Testing Determine a product MEET business expectation MINIMIZE the risk of error occursThursday, 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 correctThursday, 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 bugThursday, 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 fixedThursday, October 18, 12
  76. What are testing types you know?Thursday, October 18, 12
  77. Testing TypesThursday, October 18, 12
  78. Testing Types Unit testingThursday, October 18, 12
  79. Testing Types Unit testing Integration testingThursday, October 18, 12
  80. Testing Types Unit testing Integration testing System testingThursday, October 18, 12
  81. Testing Types Unit testing Integration testing System testing User Acceptance testingThursday, October 18, 12
  82. Testing Types Unit testing Integration testing System testing User Acceptance testing Regression testingThursday, October 18, 12
  83. Testing Types Unit testing Integration testing System testing User Acceptance testing Regression testing Performance testingThursday, October 18, 12
  84. Testing Types Unit testing Integration testing System testing User Acceptance testing Regression testing Performance testing Security testingThursday, October 18, 12
  85. Testing Types Unit testing Integration testing System testing User Acceptance testing Regression testing Performance testing Security testing Usability testingThursday, October 18, 12
  86. Testing Types Unit testing Integration testing System testing User Acceptance testing Regression testing Performance testing Security testing Usability testing Compatibility testingThursday, October 18, 12
  87. Testing Types A C B D E F GThursday, October 18, 12
  88. Testing Types A C B D Module E F GThursday, October 18, 12
  89. Testing Types Integrate A C B D Module E F GThursday, October 18, 12
  90. Testing Types Integrate A C B D Module E F G SystemThursday, October 18, 12
  91. Testing TypesThursday, October 18, 12
  92. Test CaseThursday, October 18, 12
  93. Test Case inputs to test system and verify with expected outputsThursday, October 18, 12
  94. Test Case inputs to test system and verify with expected outputs Test Case = Test Rule + Test DataThursday, October 18, 12
  95. Test IterationsThursday, October 18, 12
  96. Test Iterations Test to PassThursday, October 18, 12
  97. Test Iterations Test to Pass Test to FailThursday, October 18, 12
  98. Test Iterations Test to Pass Test to FailThursday, 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)? SOMEONEThursday, 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 TEAMThursday, October 18, 12
  103. Whole Team ApproachThursday, October 18, 12
  104. Whole Team Approach Team commitment to qualityThursday, October 18, 12
  105. Whole Team Approach Team commitment to quality Team responsible for testingThursday, October 18, 12
  106. Whole Team Approach Team commitment to quality Team responsible for testing Tester get support, trainingThursday, October 18, 12
  107. Whole Team Approach Team commitment to quality Team responsible for testing Tester get support, training Developers doing testing activitiesThursday, 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 pairThursday, 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 personThursday, October 18, 12
  110. Team Organization Traditional Organization xA Tester DevThursday, October 18, 12
  111. Team Organization Agile Organization Domain Expert Dev TesterThursday, October 18, 12
  112. 3Cs Card Conversation ConfirmationThursday, October 18, 12
  113. Test INFECTEDThursday, October 18, 12
  114. Quality Improvement by found defect EARLYThursday, October 18, 12
  115. Automate Testing in the RIGHT timeThursday, October 18, 12
  116. Don’t tell your team, WE DO AGILEThursday, October 18, 12
  117. Process’n ClockThursday, October 18, 12
  118. We don’t build the software We make it work with QUALITYThursday, October 18, 12
  119. Quality in every phase, Not afterthoughtThursday, October 18, 12
  120. Keep in touch email: zyracuze@gmail.com twitter: @zyracuze facebook: zyracuze blog: www.welovebug.comThursday, October 18, 12
  121. Thanks YouThursday, October 18, 12

×