Google Testing Blog
- Arrange Your Code to Communicate Data Flow
- Tech on the Toilet: Driving Software Excellence, One Bathroom Break at a Time
- SMURF: Beyond the Test Pyramid
- Write Change-Resilient Code With Domain Objects
- Less Is More: Principles for Simple Comments
- In Praise of Small Pull Requests
- Don't DRY Your Code Prematurely
- Avoid the Long Parameter List
- Test Failures Should Be Actionable
- isBooleanTooLongAndComplex
- How I Learned To Stop Writing Brittle Tests and Love Expressive APIs
- Prefer Narrow Assertions in Unit Tests
- What’s in a Name?
- Increase Test Fidelity By Avoiding Mocks
- Let Code Speak for Itself
- Exceptional Exception Handling
- Clean Up Code Cruft
- Write Clean Code to Reduce Cognitive Load
- Include Only Relevant Details In Tests
- Simplify Your Control Flows
- Improve Readability With Positive Booleans
- Shell Scripts: Stay Small & Simple
- The Secret to Great Code Reviews: Respect Reviewers' Comments
- Communicate Design Tradeoffs Visually
- Else Nuances