Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (8)
Similaire à Gabriele Lana: Testing Web Applications
Similaire à Gabriele Lana: Testing Web Applications (20)
Plus de Francesco Fullone
Plus de Francesco Fullone (20)
Dernier
Dernier (20)
Gabriele Lana: Testing Web Applications
- 1. Testing Web Applications Gabriele Lana www.gabrielelana.it info@gabrielelana.it
- 2. Debug Sucks Test Rocks
- 5. Hard To Change Costo Costo x Modifica nel Tempo Tempo
- 6. Always Change 60%-80% of all software is developed after first release to production
- 7. Reject Change Costo x Modifica Costo Insostenibile E' impossibile lavorarci! Rifacciamolo! Tempo
- 8. Automatic Test What = Test How = Code
- 9. Embrace Change Costo Tempo
- 10. Embrace Change = Sostenibilità
- 11. Bug Fixing
- 13. Bug Fix Costo #Bugs
- 14. #Bugs? Costo Totale = Costo (Numero Bugs)? X (Costo del singolo Bug) #Bugs
- 15. How Hard To Fix?
- 16. How Hard To Fix? Costo Costo Totale = (Numero Bugs)? X (Costo del singolo Bug)? #Bugs
- 17. Bug Repellent
- 18. Automatic Test Costo Lines Of Code
- 19. Automatic Test Costo Lines Of Code
- 20. Defect Prevention = Prevedibilità
- 21. Defect != Bug
- 22. Planning
- 24. Feedback
- 25. Sensing Code (Unit Tests)
- 26. Sensing Architecture (Functional Tests)
- 28. Do Learn Sense
- 29. Feedback = Governabilità
- 30. Automatic Tests => Sostenibilità Prevedibilità Governabilità
- 31. Test Automation Lifecycle
- 32. Fixture All the things we need to have in place in order to run a test and expect a particular outcome
- 33. 1: Fixture SetUp Fixture Fixture SetUp
- 34. SUT The “System Under Test”, whatever thing we are testing
- 35. 2: Exercise SUT Fixture Fixture SetUp Exercise SUT SUT
- 36. 3: Verify Result Fixture Fixture SetUp Exercise SUT SUT Verify Result
- 38. 4: Fixture TearDown Fixture Fixture SetUp Exercise SUT SUT Verify Result Fixture TearDown
- 39. Test Automation Identity
- 40. Tools
- 41. Who? What? Why?
- 42. Who? Chi lo scrive? A chi da valore? Chi lo legge?
- 43. What? Quali sono le Qual'è il SUT? condizioni?
- 44. Why? Qual'è lo scopo? Cosa voglio verificare? Quali informazioni voglio avere?
- 45. Unit Tests
- 46. Who? Developers
- 48. Why? Verify Code Behaviour, Code Documentation
- 49. Unit Test Test Function • Method • Unit Procedure • ... •
- 50. Unit Test Database • File System Test • Configuration • X OS • Unit
- 51. Unit Test Test X Network X Unit
- 52. Unit Test Test X X X Unit Unit
- 53. Tools Simple Test (http://www.lastcraft.com/simple_test.php) PHPUnit (http://www.phpunit.de)
- 55. 1: Fixture SetUp
- 56. 2: Exercise SUT
- 57. 3: Verify Result
- 60. If total() < 100 then no discount If daysUntilLastSelling() > 30 then no discount If daysUntilLastSelling() < 30 and total() > 100 then discount
- 61. New Requirement
- 62. If total() < 100 then no discount If daysUntilLastSelling() > 30 then no discount If daysUntilLastSelling() < 30 and total() > 100 then discount
- 63. Embrace Change?
- 64. Test Behaviour Not Code
- 65. If total() < 100 then no discount If daysUntilLastSelling() > 30 then no discount If daysUntilLastSelling() < 30 and total() > 100 then discount
- 67. If total() < 100 then no discount If daysUntilLastSelling() > 30 then no discount If daysUntilLastSelling() < 30 and total() > 100 then discount
- 69. If total() < 100 then no discount If daysUntilLastSelling() > 30 then no discount If daysUntilLastSelling() < 30 and total() > 100 then discount
- 70. Why? Test Driven Development = Code Design
- 71. Code Coverage
- 72. Integration Tests
- 73. Who? Developers
- 75. Why? Verify Code Behaviour, Code Documentation, Code Design
- 76. Database Tests
- 78. What? Stored Procedure, Complex Query, Data Migration
- 79. Why? Wrong data is source of bugs!
- 80. Functional Tests
- 81. Who? Developers, Customer
- 83. Why? Verify Application Behaviour, Application Design
- 84. What? HTTP
- 85. Tools Selenium (http://www.openqa.org/selenium)
- 94. What? HTTP
- 95. What? Presentation Vs Business Logic
- 96. Acceptance Tests
- 97. Who? Customer
- 99. Why? Product Design, Product Specification
- 100. Tools Fit/Fitness/PHPFit (http://fit.c2.com/) (http://fitnesse.org/) (http://phpfit.berlios.de/)
- 108. Where? When? Run Automatic Tests
- 110. When?/Where? Unit Tests, Integration Tests, Database Tests, Acceptance Tests
- 113. When?/Where? (All Previous) + Smoke Tests
- 115. When?/Where? (All Previous) + Load/Performance/Security Tests + Migration/Installation/Configuration Tests
- 116. Test Automation Genesis
- 117. Risk Analysis
- 118. Brian Marick Cathegories Business Facing Support Programming Support Product Technology Facing
- 119. Brian Marick Cathegories Business Facing Support Programming Support Product Unit Tests Technology Facing
- 120. Brian Marick Cathegories Business Facing Support Programming Support Product Acceptance Tests Unit Tests Technology Facing
- 121. Brian Marick Cathegories Business Facing Support Programming Support Product Acceptance Tests Load/ Unit Security Tests Tests Technology Facing
- 122. Automatic Business Facing Support Programming Usability/ Support Product Acceptance Exploratory Tests Tests Load/ Unit Security/ Tests Tests Technology Facing
- 123. All Tests should be Automatic?
- 124. Manual Business Facing Support Programming Usability/ Support Product Acceptance Exploratory Tests Tests Load/ Unit Security/ Tests Tests Technology Facing
- 125. Manual Tests Drive Automatic Tests
- 126. Test Automation
- 127. Pay Attention to Test Automation
- 128. “An imperfect test today is better than a perfect test someday”
- 129. Test Automation = Process Improvement
- 130. Debug Sucks Test Rocks
- 132. Testing Web Applications Gabriele Lana www.gabrielelana.it info@gabrielelana.it