How Much Testing Is Enough Testing

This was first presented at GovTech's STACK2020 Virtual Conference, from 01-03 Dec 2020.

The recording of the presentation may be found at GovTech's Developer Portal [here]{https://www.developer.tech.gov.sg/communities/events/conferences/stack-2020/overview.html} and on YouTube [here]{https://www.youtube.com/watch?v=-LDuWlIYoR8}.

Transcript

1. How Much Testing Is Enough Testing Samantha Wong GovTech STACK 2020 - Dec 2020
2. You’ve Heard Of These Before ➔ Functional Testing ➔ Load Testing ➔ Integration Testing ➔ User Testing ➔ Smoke Testing ➔ Sanity Testing ➔ Blind Testing ➔ Whitebox Testing ➔ Blackbox Testing ➔ Unit Testing ➔ End to End Testing
3. Just because there is a name for it, doesn’t mean it exists
5. So, how?
6. You should choose which testings to focus on based on your acceptable risks High-traffic user flows like a promotional flow on an e-commerce website
7. You should choose which testings to focus on based on the nature of your application End-to-end testings with your third party agencies
11. People Who Define The Application and Its Acceptable Risks
12. How to guarantee the quality of tests Designing (good) tests are hard!
13. Tests check that expectations are met
14. Tests alert when expectations are not met
15. Know What You Are Testing
16. More Doesn’t Mean Better
17. Because...Sometimes They Are The Same
18. Write Tests Before Development
19. The Spheres of Knowing Stuff I know I know Stuff I didn’t know I know Stuff I know I don’t know Stuff I didn’t know I didn’t know
20. Verify Your Tests Do Something
21. [Example on Unit Testing] https://jeroenmols.com/blog/2017/11/28/coveragproblem/
22. [Example Function Tested] https://jeroenmols.com/blog/2017/11/28/coveragproblem/
23. [Modified Test]
24. Good tests should break when things fail
25. Don’t trust code coverage tools One more thing.. They are a source of information, not a source of quality.
26. End Slide