Testing the limits of testing

Download Testing the limits of testing

Post on 05-Dec-2014

357 views

Category:

Technology

0 download

Embed Size (px)

DESCRIPTION

 

TRANSCRIPT

<ul><li> 1. Testing the limits of testing Phil Robinson LonsdaleSystems.com LonsdaleSystems.com 1 </li> <li> 2. Teaching software testing Blah blah blah blah In theory there is no difference between theory and practice. In practice there is. Yogi Berra LonsdaleSystems.com 2 </li> <li> 3. The project LonsdaleSystems.com 3 </li> <li> 4. The project objective Front End (ASP) Transaction Queue Back End (PL/SQL) Front End (Oracle ADF) LonsdaleSystems.com Database Transaction Queue (Oracle AQ) 4 </li> <li> 5. The project plan Testing Project Deadline LonsdaleSystems.com 5 </li> <li> 6. The test strategy LonsdaleSystems.com 6 </li> <li> 7. Analysis Design The waterfall mantra Code Test Unit Integration System Acceptance LonsdaleSystems.com 7 </li> <li> 8. Testing is actually three different activities Test Design Test Execution Defect Repair LonsdaleSystems.com 8 </li> <li> 9. Testing is about quality not project phases Fit for intended purpose Conform to spec Absence of Defects and other quality goals LonsdaleSystems.com 9 </li> <li> 10. Testing objectives Validate that the software is fit for its intended purpose Verify that the software conforms to its specification Identify failures caused by defects Measure non-functional attributes of the software (security, performance, reliability) Build confidence in the software LonsdaleSystems.com 10 </li> <li> 11. Testing objectives Test to pass Validate Verify Measure Build confidence LonsdaleSystems.com Test to fail Identify failures Measure (stress) 11 </li> <li> 12. Vertical integration Unit test LonsdaleSystems.com 12 </li> <li> 13. Vertical integration Integrate LonsdaleSystems.com 13 </li> <li> 14. Vertical integration Unit test LonsdaleSystems.com 14 </li> <li> 15. Vertical integration Integrate LonsdaleSystems.com 15 </li> <li> 16. Vertical integration Unit test LonsdaleSystems.com 16 </li> <li> 17. Vertical integration Integrate LonsdaleSystems.com 17 </li> <li> 18. Horizontal integration Database Feature LonsdaleSystems.com Feature Feature Feature 18 </li> <li> 19. Horizontal integration Database Feature LonsdaleSystems.com Feature Feature Feature 19 </li> <li> 20. Testing should not be black and white Black-box Functional Specification based LonsdaleSystems.com White-box Structural Code based 20 </li> <li> 21. Designing test cases Spec Code Test Basis Test Item Test Cases Other Docs Existing System LonsdaleSystems.com 21 </li> <li> 22. A Better way to define test strategy Test Item Test Basis Spec Code Other docs Existing systems Objective LonsdaleSystems.com Fit for intended purpose Conform to spec Identify failures Measure nonfunctional attributes Build Confidence Who? Developer Technical specialist Test Analyst Business Analyst Subject matter expert 22 </li> <li> 23. Early and extensive unit testing LonsdaleSystems.com 23 </li> <li> 24. Minimal unit testing System Coding LonsdaleSystems.com 24 </li> <li> 25. Minimal unit testing System Test Quality acceptable for user involvement Acceptance Test Project Deadline LonsdaleSystems.com 25 </li> <li> 26. Extensive unit testing System Coding LonsdaleSystems.com Unit Testing 26 </li> <li> 27. Extensive unit testing System Test Verify conforms to spec Acceptance Test Quality acceptable for user involvement LonsdaleSystems.com Validate fit for intended purpose Project Deadline 27 </li> <li> 28. One in three developers dedicated to unit testing 66% coding full time 33% testing full time LonsdaleSystems.com 28 </li> <li> 29. Feature testing LonsdaleSystems.com 29 </li> <li> 30. Feature testing to build confidence Feature Feature Feature Feature Testing Feature LonsdaleSystems.com 30 </li> <li> 31. Modelling features Feature Feature Test Case Test Case Feature Test Case Feature Test Case Feature LonsdaleSystems.com Test Case 31 </li> <li> 32. End-to-end testing LonsdaleSystems.com 32 </li> <li> 33. End-to-end verification of business rules Feature LonsdaleSystems.com Feature Feature Feature 33 </li> <li> 34. End-to-end verification of business rules Feature LonsdaleSystems.com Feature Feature Feature 34 </li> <li> 35. Modelling business rules e ur at Fe e ur at Fe e ur at Fe State State Choice State LonsdaleSystems.com State State 35 </li> <li> 36. Generating scenarios e ur at Fe e ur at Fe e ur at Fe Scenario State LonsdaleSystems.com 36 </li> <li> 37. Date-based testing LonsdaleSystems.com 37 </li> <li> 38. Date-based testing Scenario 1 Period 1 Period 2 Period 3 Scenario A Feature Feature Feature Feature Feature Feature 2 Scenario B Feature Feature Feature Feature 3 Scenario C LonsdaleSystems.com Feature Feature 38 </li> <li> 39. Exploratory testing LonsdaleSystems.com 39 </li> <li> 40. Encouraging testers to get creative 20% Testing skills Subject matter expertise 80% Build confidence Verify business rules Test Cases LonsdaleSystems.com 40 </li> <li> 41. Triaging bugs LonsdaleSystems.com 41 </li> <li> 42. Triaging bugs Test Execution Spreadsheet Spreadsheet JIRA Spreadsheet LonsdaleSystems.com 42 </li> <li> 43. Triaging bugs Bugs Re e ort p d Duplicates Vague descriptions Cant duplicate Tester misunderstanding Resolved Time LonsdaleSystems.com 43 </li> <li> 44. Still teaching software testing Coming in 2014 Practical Software Testing LonsdaleSystems.com LonsdaleSystems.com 45 </li> <li> 45. Questions LonsdaleSystems.com LonsdaleSystems.com 46 </li> </ul>