[DevDay 2017] Why automated testing is not (only) about correctness - Speaker: Steffen Frank - Project Manager at mgm technology partners
•
0 j'aime•1,181 vues
Automated testing is often seen as "what testers do, i.e. searching for bugs, but automated" But automated testing is also (and mainly!) - About non-functional requirements (performance, fault tolerance, ...) - A form of specification (versioned with the code, executable, more durable than the requirement documents) - A design tool for APIs and interfaces - A necessary precondition for scalability and longevity of a software product This talk will give you information about some benefits of automated tests that are commonly underrated
Recommandé
Recommandé
Contenu connexe
Similaire à [DevDay 2017] Why automated testing is not (only) about correctness - Speaker: Steffen Frank - Project Manager at mgm technology partners
Similaire à [DevDay 2017] Why automated testing is not (only) about correctness - Speaker: Steffen Frank - Project Manager at mgm technology partners (20)
Plus de DevDay.org
Plus de DevDay.org (20)
Dernier
Dernier (20)
[DevDay 2017] Why automated testing is not (only) about correctness - Speaker: Steffen Frank - Project Manager at mgm technology partners
- 1. München/HQ Bamberg Berlin Đà Nẵng Dresden Grenoble Hamburg Cologne Leipzig Nuremberg Prague Washington Zug Why test automation is not (only) about bugs The true benefits of test automation Steffen Frank
- 2. 13.04.17 2 20 years of IT experience Worked for different industries Energy trading, Automotive, Wholesales, NGO, … Worked in different roles Developer, Tester, Product manager, Scrum master Steffen Frank steffen.frank@mgm-tp.com
- 3. 13.04.17 3 mgm technology partners We build software § Web & mobile § Large enterprise customers in Germany We use state of the art technologies § JEE, Spring, Hibernate § Angular, REACT § Postgres, Oracle
- 4. 13.04.17 4 We are proud of our engineers 500+ Engineers world wide
- 5. 13.04.17 5 We are proud of our engineers in Vietnam 38 engineers since January 2016
- 6. 13.04.17 6
- 7. 13.04.17 7
- 8. 13.04.17 8
- 9. 13.04.17 9
- 10. 13.04.17 10
- 11. 13.04.17 11
- 12. 13.04.17 12
- 13. 13.04.17 13
- 14. 13.04.17 14
- 15. 13.04.17 15 Unit test example
- 16. 13.04.17 16 Mocking in integrations tests - example
- 17. 13.04.17 17 End to end test example
- 18. 13.04.17 18
- 19. 13.04.17 19
- 20. 13.04.17 20
- 21. 13.04.17 21
- 22. 13.04.17 22
- 23. 13.04.17 23
- 24. 13.04.17 24 Requirement documentation, a simple example
- 25. 13.04.17 25 The requirement, written as a test:
- 26. 13.04.17 26
- 27. 13.04.17 27
- 28. 13.04.17 28
- 29. 13.04.17 29
- 30. 13.04.17 30
- 31. 13.04.17 31
- 32. 13.04.17 32 Code examples taken from public websites § Junit Tests example from http://www.vogella.com/tutorials/JUnit/article.html § HTTP Mocking example from http://wiremock.org/docs/getting-started/ Further reading § Test-pyramid https://martinfowler.com/bliki/TestPyramid.html § Unit testing overview https://www.slideshare.net/tom.zimmermann/unit-testing-with-junit § Integration testing example: http://javawithravi.com/rest-api-integration-testing-with-wiremock/ § End to end testing: https://jaxenter.com/tutorial-groovy-functional-testing-with-geb-104382.html § Test driven design: https://www.youtube.com/watch?v=qkblc5WRn-U § Very early testing: http://blog.mgm-tp.com/2015/06/very-earling-testing1/ Links and sources
- 33. 13.04.17 33 Innovation Implemented. mgm technology partners GmbH Frankfurter Ring 105a 80807 München Tel.: +49 (89) 35 86 80-0 Fax: +49 (89) 35 86 80-288 http://www.mgm-tp.com PragMunich Berlin Hamburg Cologne NurembergGrenoble LeipzigDresdenBamberg Đà Nẵng ZugWashington