Google Testing Blog: Testing on the Toilet: Test Behaviors, Not Methods
testing.googleblog.com · 1,923 words · saved by 1 readers
by Erik Kuefler This article was adapted from a Google Testing on the Toilet (TotT) episode. You can download a printer-friendly version ...
Google Testing Blog: Testing on the Toilet: Test Behaviors, Not Methods Testing Blog Testing on the Toilet: Test Behaviors, Not Methods Monday, April 14, 2014 Google Labels: Erik Kuefler , TotT 6 comments : Infant Gerald April 14, 2014 at 5:40:00 PM PDT Thanks as a QAE, I was so tempted to write all my validations in a single test esp when there is a continous flow happening. Now that temptations has eased. Howeve this because more challenging when we write UI Tests with a lot of inputs before it even lands on the page to test. Where is the line to be drawn before going crazy and write a
related reading
- Software Engineering at Googleabseil.io
- GitHub - abhivaikar/howtheytest: A collection of public resources about how software companies test their softwaregithub.com
- Google Testing Blogtesting.googleblog.com
- GitHub - mawrkus/js-unit-testing-guide: 📙 A guide to unit testing in Javascriptgithub.com
- Google Testing Blog: Code Healthtesting.googleblog.com
- https://danluu.comdanluu.com
- UI Skills for Design Engineers | UI Skillsui-skills.com
- Meticulous AI - Automated Frontend Testing Without Writing Testsmeticulous.ai
- Reading 2: Testingweb.mit.edu
- Why Good Developers Write Bad Unit Tests · mtlynch.iomtlynch.io
- Enabling Agent 3 to Self-Test at Scale with REPL-Based Verificationblog.replit.com
- Google Testing Blog: Communicate Design Tradeoffs Visuallytesting.googleblog.com