![Unit Test VS End to End Test Domenico Musto @mimmozzo [email_address]](https://image.slidesharecdn.com/unittestsvsendtoendtests-111121140028-phpapp01/85/Unit-Tests-VS-End-To-End-Tests-1-320.jpg)
![Chi é costui ? .NET Web REST Agile Automation Testing C# Team leading @mimmozzo [email_address] Ruby](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
Viewers also liked
Viewers also liked (14)
Similar to Unit Tests VS End To End Tests
Similar to Unit Tests VS End To End Tests (20)
More from mimmozzo_
More from mimmozzo_ (9)
Unit Tests VS End To End Tests
- 1. Unit Test VS End to End Test Domenico Musto @mimmozzo [email_address]
- 2. Chi é costui ? .NET Web REST Agile Automation Testing C# Team leading @mimmozzo [email_address] Ruby
- 5. Test e QA
- 7. Libraries
- 8. The Agile Testing Quadrant
- 11. Functional
- 12. Load
- 13. Soak
- 18. Sono veloci da eseguire
- 20. Non abusare del mocking
- 22. Il “trigger” é l'implementazione di un “requirement”.
- 27. Usare context builders per il setup di data fixture
- 29. Danno informazioni sui limiti di carico
- 30. Sono complessi da scrivere
- 33. Sono lenti
- 36. Integration
- 37. Exploratory
- 39. Fungono da acceptance tests
- 40. Sono comprensibili a chi non conosce il codice
- 50. QA
- 51. Cliente
- 52. La storia
- 70. Functional Test
- 71. Integration Test
- 72. Unit Test
- 76. Modifiability
- 77. Performance
- 78. Security
- 79. Testability
- 80. Usability
- 81. The test pyramid
Editor's Notes
- Test affidabili = deploy facile