Move fast while maintaining quality with black box testing (talk)
Some systems are hastily built → No automated tests → Code became tightly coupled → Code became difficult to test → Want to improve the code but afraid of improving due to fear that it might break because there are no automated tests. In this talk, I share some ideas on how I try to get out of this loop.
Transcripthttps://creatorsgarten.org/videos/bkkjs17/blackbox
References
Introductions
- Somkiat Puisungnoen (2015), "ขอโทษนะ !! ยังจะทดสอบแบบ Manual เป็นหลักกันอยู่อีกหรือ ?"
- Charity Majors (2021), "It is time to fulfill the promise of Continuous Delivery."
- David Heinemeier Hansson (2014), "Test-induced design damage."
Testing Pyramid vs Testing Trophy
- Mike Wacker (2015), "Just Say No to More End-to-End Tests," Google Testing Blog.
- Kent C. Dodds (2018), "The Testing Trophy"
More opinion on testing approaches
- Dave Farley (2022), "Don't Do E2E Testing!" Continuous Delivery.
- Theo Browne (2022), "Why I Don't Unit Test."
More testing pyramids
- Seb Rose (2020), "Eviscerating the Test Automation Pyramid," Cucumber Blog.
- Andrew Knight (2018), "The Testing Pyramid," Automation Panda.
- Devesh Bajpai (2018), "Agile Testing: Test Pyramid and BDD."
Making things easy to test
- Example of service menu in arcade games: [1], [2]
- Samsung's diagnostic menu
- Kent C. Dodds (2020), "Make your own DevTools."
- Bemuse's playground page and Bemuse Song Workshop's unit tests page.
Playwright
Testing in production
- Michael Bryzek (2017), "Testing in Production - Quality Software Faster," QCon San Francisco 2017.