Issue #100 : Software Testing Notes
Successful collaborative testing sessions
Hello there! 👋
Welcome to the 100th 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.
Consider subscribing if you haven’t already👇
I can’t believe we have made it so far. We are at the #100th Issue of the newsletter.
I started this newsletter around ~2.5 years ago with only me as a sole subscriber and reader for the first couple of months. we have come a long way after that.
As of today, we have more than ~1100 active people getting the newsletter with ~1500 articles and resources curated so far.
1100 is a small number compared to the lifespan of the newsletter or other newsletters in the testing space. But it’s still a huge win for me personally as this has allowed me to connect with much wider community. I regularly get one or two emails every week sharing their view on a article I curated, sharing reading recommendation and much more.
I would like to thank each and everyone of you for reading this newsletter and being such a kind hearted audience to interact with.
🙏 Supported by
Curated collection of the 350+ best hand-picked tools on the internet to supercharge your testing. - TestDev.Tools
TestDevTools is a collection of 350+ hand-picked tools & resources for your every testing needs. Whether you're looking for a new Automation tool, framework alternatives, a new way to manage test data, a way to learn development or testing… We got you covered.
Having collaborative testing sessions with relevant stockholders is one of the most effective way of enhancing your testing. Ben Dowen has written very insightful article detailing what you could do make these kind of sessions more effective.
I have came across many teams reducing the QA by making developers write more Unit tests as it is considered best practice and they tend to assume that since unit tests are passing there is not that much to do with other type of tests. Titus Fortner explains much better than me in this article along with how this QA vs Dev focus testing inevitably affects one of the core area of testing → Integration testing.
This is a second installment of four part series exploring attributes of testability. In this article Gil Zilberfeld explores how easily we can observe the result or effect of the operation.
Also, take a look at the part 1 discussing first attribute - Operability.
David Burns draws interesting parallel between how testing is carried out in software and automobile industry. Worth the read.
Karunakar has written some nice pointers about some important key characteristics of Exploratory Testing, It’s advantages, challenges and tips to make Exploratory Testing more effective.
➜ Read all curated stuff on Software Testing.
There are lots of ways to start snapshot testing for your android app and there are many libraries you can use. But how do you know what is the best option for you? Thankfully, Sergio Sastre Florez has written a great article exploring some of the most popular libraries along with their uses and limitations.
Sorry-cypress is an open-source alternative to the Cypress Dashboard for recording, managing, and analyzing your Cypress test runs.
In this article, compares “Sorry Cypress” and “Cypress Cloud” and shows step by step process of implementing Sorry-cypress for your cypress test automation.
Laravel Dusk provides an expressive, easy-to-use browser automation and testing API.
IF you are testing for Laravel app, Laravel Dusk might be the better solution to automate testing compare to Selenium. Simon Rusin shares some nice insights about it in this article along with how you can get started with automation testing with Laravel Dusk.
This is a step by step guide to get started with unit testing and UI testing for iOS by writing Unit tests. Nicely written article by Shilpriya Shah explaining the step by step process with code examples and explanation of each code fragment.
➜ Read all curated stuff on Software Testing Automation.
Finding Balance in Complexity: A Performance Engineer’s Guide to the Pareto Principle by Hariprabu Kandasamy
Pareto Principle (“80/20 rule”) states 80% of all outcomes are derived from 20% of causes. But, how does this principle manifest within the context of performance engineering? Read this great post by Hariprabu Kandasamy to find out.
Dan Torres shares some nice tricks to integrating memory leak tracking into unit tests.
➜ Read all curated stuff on Performance Testing.
🛠️ Resources & Tools
WebPerf-Snippets — A curated list of snippets to get web performance metrics to use in the browser console or as snippets in Chrome's DevTools.
a11y-ai — An experimental tool to automatically detect accessibility issues in web pages using OpenAI and provide suggestions for fixing them.
CrowdView — A search engine that lets you conduct a search exclusively on forum websites (Stack Overflow, Hacker News, Reddit, etc).
📝 List of Software Testers
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.
🎁 Bonus Content
📌 OTHER INTERESTING STUFF
⭐ LAST WEEK'S MOST READ
😂 And Finally,
Keep Smiling and have a fun week.
📨 Send Me Your Articles, Tutorials, Tools!
Thanks to everyone for subscribing and reading!