Why you shouldn't pay too much attention to your code coverage
Argues against using code coverage as a strict target, explaining why high coverage doesn't guarantee good tests and can misdirect developer effort.
Argues against using code coverage as a strict target, explaining why high coverage doesn't guarantee good tests and can misdirect developer effort.
A survey analysis on how the practice of Specification by Example has evolved over the decade since the author's book, focusing on its impact on product quality.
A guide offering 10 practical tips for writing clearer, more maintainable, and effective software tests, focusing on documentation and isolation.
Article argues that code quality directly impacts user experience by enabling faster feature delivery and fewer bugs.
Explores the benefits of functional programming and F# for improving code correctness and maintainability in C# teams.
A guide on effective software testing: write tests, avoid 100% coverage, and focus on integration tests for confidence.
An introduction to code coverage, explaining how to read it and use it effectively in your testing workflow, with practical examples using Jest.
A developer argues for the benefits of 100% unit test coverage, addressing common counterarguments and emphasizing testable code design.
A dual perspective on rOpenSci's open peer-review process for R packages, from both reviewer and package author viewpoints.
The article argues against nitpicking in code reviews by advocating for automated style checks to improve efficiency and focus.
A critical review of Spotify's web, desktop, and mobile apps, highlighting numerous bugs, localization errors, and usability issues.
Explains why smaller code reviews are more effective and offers practical strategies for splitting large patches into manageable pieces.
Explores how open source software acts like Yelp, shifting power from publishers to consumers by amplifying user feedback and demanding higher standards.
Author announces the end of the 'Browsers and Bugs' newsletter due to lack of feedback, reflecting on its content about browser bugs, features, and testing.
A literature review examining empirical studies on the impact of static vs. dynamic typing on software quality, finding mostly small effects.
A developer lists the 7 most common code quality issues found during code reviews, focusing on maintainability and best practices.
Explains why common Ruby unit tests are flawed and demonstrates proper unit testing with mocks and stubs for isolation.
A developer discusses a pragmatic approach to bug fixing using test cases, emphasizing the importance of verifiable bug reproduction in version control.