Three Ways To Measure Unit Testing Effectiveness
Unit testing is the foundation of the test pyramid. Eduardo Fischer suggests three ways of assessing how effective your unit tests are using metrics and tools.
Ryan Craven describes the common metrics for measuring test automation coverage, explaining its pros and cons and why it depends on different contexts.
And once you start improving your coverage, beware of the Flakey UI automation.
Note: If you can't access the full article, simply open it in a private tab.
Whole-team approach to quality is one of the main agile testing principles. Ryan Craven shares his experience of joining a team with that mindset and what impact it had.
On top of that, you might be interested in implementing some Metrics for Testing — Guide to Quality Assurance as Aroni Das explains.
Introducing a QA Process to a new team
Joining a new team and wondering how to kick off testing processes? There are several detailed pieces of advice from the testing community on what to do.
Furthermore, Katja Obring shares a perspective of The Solo Tester's Dilemma: When Enterprise Metrics Don't Fit.
When the build is green, the product is of sufficient quality to release
Mirek Długosz warns about the risk of relying on a single metric to decide on release readiness and advises on how to improve this process.
Additionally, José Carréra wrote a great article about: Are You Seeing RED? Restoring Reliability To Test Results.
"Bug counts are a measurement of nothing else than how many bugs your team are reporting; code coverage only tells you how much of your code is completely untested or unreachable; and test pass rates…are mostly useless."
I enjoyed Alan Page's take on the common problems with metrics and his advice on how to approach it right. A recommended read for your testing team.
How can I trust my test suite?
Great question! Antonello D'Ippolito suggests using some metrics and indicators that can help you assess the confidence in your tests.
Also, Paul Grizzaffi wrote about Asserting Them Softly — Soft Asserts In Practice, explaining how it can help you better understand the failing tests in a test suite.
Welcome to the 268th issue!
Quality is hard to measure.
But the activities impacting quality can be measured, such as development practices, technical debt or test coverage.
That's where QE Score comes in.
Simon Champenois created it to pragmatically collect and track metrics in one place.
To learn more, check out Simon's article about Quality Engineering, Quantified: What Your QE Score Really Means.
Happy testing! 🙂
Use Playwright tests to monitor your apps with Checkly!
Checkly lets you easily deploy high-quality Playwright scripts to monitor Apps, Websites & APIs, from Dev to Production. Validate crucial user flows, collect error traces, screenshots and performance metrics, and understand how your app performs for users across the globe! Start for free!
Welcome to the 171st issue!
Since the beginning of this newsletter, I've featured well over 4,000 articles and other resources on software testing.
And they're all stored online.
So if you want to learn more about a particular topic you're interested in, simply use the Search function.
For example, here are the results for metrics, Playwright or test strategy.
Hope that helps you discover even more great news.
Happy testing! 🙂
