Use Testing to Develop Better Software Faster

Testing doesn’t always get the attention it deserves in software development. Many developers claim to be bad at it, or are just not that interested. (These may or may not be related.)

As developers, our job is to deliver working software. With the shift to CI/CD and the move to the cloud, the need to have the right feedback at the right time only increases. There are many ways that testing can help us with that. Not only can testing help us verify our solution and prevent us from breaking things, it can also help us design our software, find flaws in our architecture and come up with better solutions. In this talk I will highlight some of the many ways that testing can help you to develop better software faster.

Transcript

1. @MaritvanDijk77 
 github.com/mlvandijk 
 https://maritvandijk.com/ Use Testing to Develop Better Software Faster Voxxed Days Cluj-Napoca - Oct 6th, 2022
2. Some tests… @MaritvanDijk77
3. @MaritvanDijk77
4. @MaritvanDijk77
5. Build quality in @MaritvanDijk77
6. https://danashby.co.uk/2016/10/19/continuous-testing-in-devops/ @MaritvanDijk77
7. https://janetgregory.ca/testing-from-a-holistic-point-of-view/ @MaritvanDijk77
8. @MaritvanDijk77
9. The right feedback at the right time @MaritvanDijk77
10. Ask questions @MaritvanDijk77
11. @MaritvanDijk77
12. @MaritvanDijk77
13. https://elizabethzagroba.com/posts/2019/2019-01-25_have-i-tried-enough-weird-stuff/ @ezagroba @MaritvanDijk77
14. @MaritvanDijk77
15. https://github.com/minimaxir/big-list-of-naughty-strings @MaritvanDijk77
16. https://twitter.com/sempf/status/514473420277694465?s=20&t=ZDqpc0arpJZeUBL6M1J3jg https://www.sempf.net/post/On-Testing1 @MaritvanDijk77
17. How are we going to test this? @MaritvanDijk77
18. Test pyramid @MaritvanDijk77 https://martinfowler.com/bliki/TestPyramid.html
19. @MaritvanDijk77
20. Build testability in @MaritvanDijk77
21. “When developers are involved in creating and maintaining acceptance tests: 1. code becomes more testable (this is why TDD is important) 2. they will care more and invest more effort into maintaining & fixing them.” From Accelerate by Nicole Forsgren, PhD Jen Humble, and Gene Kim
22. Use the right tools @MaritvanDijk77
23. @MaritvanDijk77
24. Use tools as intended @MaritvanDijk77
25. Tests should increase confidence @MaritvanDijk77
26. @MaritvanDijk77
27. Tests should be reliable @MaritvanDijk77
28. @MaritvanDijk77
29. @MaritvanDijk77
30. Run your tests @MaritvanDijk77
31. Run your tests @MaritvanDijk77
32. Never trust a test you haven’t seen fail @MaritvanDijk77
33. @MaritvanDijk77
34. A failing test should tell you exactly what’s wrong quickly @MaritvanDijk77
35. @MaritvanDijk77 @MaritvanDijk77 @KevlinHenney at GoTo Amsterdam
36. Each test should test one thing @MaritvanDijk77
37. Use meaningful, descriptive names @MaritvanDijk77
38. @MaritvanDijk77 Readability of your tests
39. @MaritvanDijk77
40. @MaritvanDijk77
41. TL; DR: Test your code! @MaritvanDijk77 https://www.redbubble.com/people/hogfish (Trish Khoo @hogfish)
42. @MaritvanDijk77 
 github.com/mlvandijk 
 https://maritvandijk.com/ Use Testing to Develop Better Software Faster Voxxed Days Cluj-Napoca - Oct 6th, 2022