This is the Software Testing Notes, a newsletter that goes out every Wednesday. I republish it here for sharing and referencing, but if you'd like to sign up you can do so right here:
Welcome the 68th edition of Software Testing Notes, a weekly newsletter featuring must-read content on Software Testing. I hope this week has been good for you so far.
I came across a blog post about avoiding git empty commits by Jeroen Pluimers. It discusses the pitfalls of using empty git commits for triggering the ci/cd pipelines. The article takes reference from Empty commits and other wrong tools for the job written by Kristian Köhntopp. I must say that I have been guilty of doing just that in the past. But one day when we were going through the logs to check for the one particular bug fix in a legacy code base and found that almost everyone was doing the same thing as me for one reason or another. And it had polluted entire commit history. And because of this mess, what should have been discovered in few minutes took almost 2 hours.
Every tooling has their specific purpose. Don’t try to use it for everything. It might work but you might also end up creating a whole set of another problems and eventually you might end up making it worse than before.
A quote from the article,
“I suppose it is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail.” — Abraham Maslow
Now, on to the this week’s curated links. I have lots of nice reads for you this week, let me know what your favorite is!
Google’s DevOps Research and Assessment team (DORA) has identified few key software delivery performance metrics to improve process quality but can influence product quality as well.
An interesting perspective by Joep Schuurkes on why reading “The Agile Manifesto” would not be a good idea as a first step to someone who want to learn about Agile and what could be the better way.
What is testability? Oleksandr Romanov looks a little bit deeper in to the context and offers some valuable insights to us as to what we as a testers could do to help enhance it.
We all know about Test Pyramid and their function(Maybe). Mirek Dlugosz discusses few problems that might arise between the team with common understanding of test levels and also shares a few useful tips that might help you to construct your own classification that could be agreed upon and used by all team members unanimously.
➜ Read all curated stuff on Software Testing here.
Do you want to know about testing Infrastructure as Code? In this post, Raghava Nelabhotla gives a brief overview of infrastructure as code, tools used to deploy and options for using tool belt to test infrastructure.
Latest release of Postman includes capability of writing test specifications for the gRPC calls. Take a look at this article by Appurva Murawat to learn how you can add tests to your gRPC requests.
In previous issue, I shared a link about how Filip Hric implemented customized solution to test PDF files. This week, Gleb Bahmutov takes this a bit further and has built upon the Filip Hric’s solution to convert pdf files to html and test it using Cypress commands.
Mocks Server — is a Node.js mock server running live, interactive mocks in place of real APIs.
This is a guide detailing how to install, configure and use Mocks Server to write api mocks. Javier Brea Alcocer also shows how we could utilize cypress commands to change the responses for the API mocks for our testing purpose.
➜ Read all curated stuff on Software Testing Automation.
It might seem easy enough to perform load test on your application. But the the real complexity lies on what kind of Load Model to construct for the load test so that it could actually mimic the real time user load. Want to know what could go wrong without proper load simulation? Mark Yang shares one such example.
➜ Read all curated stuff on Performance Testing.
Take a look at this article by S Chathuranga Jayasinghe sharing how to use cypress-axe package of cypress to write and execute automated A11Y tests along side your usual functional tests.
➜ Read all curated stuff on Accessibility Testing.
HTML Size Analyzer — Enter HTML directly or a URL to analyze HTML size and catch bloat like inline images, large React hydration state, or code duplication.
@puppeteer/replay — A library that provides an API to replay and stringify recordings created using Chrome DevTools Recorder.
Ddosify — A high-performance load testing tool, written in Go, for distributed and Geo-targeted load testing.
Mocks Server — Node.js mock server running live, interactive mocks in place of real APIs
It's hard to find good articles, podcasts on Software Testing. Even hard to find people who create them. Are you also looking for amazing software testers to follow or read their content ? check out this page dedicated to software testers.
Do you also create content around Software Testing ? Submit yours here and I will add it to the list.
📌 OTHER INTERESTING STUFF
- Rituals for Engineering Teams
- Getting comfortable with being uncomfortable
- Adaptive Thinking: The Best Way to Deal With Unexpected Situations
⭐ LAST WEEK'S MOST READ
- The two types of quality
- Testing a PDF file with Cypress
- Unit Test vs. Integration Test: How To Use Both
Keep Smiling and have a fun week.
Thanks to everyone for subscribing and reading!
Did You Enjoy This?
Then consider joining the 1,553 other people getting the Software Testing Notes newsletter. It's a collection of fascinating finds from my week, about wide range of topics surrounding software testing and whatever else catches my interest.