Issue #38 : Software Testing Notes
Helping Developers and Testers Get Along
Hello there! 👋
Welcome the 38th 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 have lots of nice reads for you this week, let me know what your favorite is!
Consider subscribing if you haven’t already 👇
Happy Testing and have a great rest of the week! 🙏
📚 On Testing
Ash Winter has created the ‘Testability Advocacy Canvas’ map/aid tool to build better visibility in testing and for those who want to become testability advocates within a team or wider organization.
The most important relationship you as a individual tester and team can have is with the developers. It's not unusual to see bickering between development and QA. Dennis Martinez shares some tips to have both teams do their best work without constant arguing.
In this article, Prashant Hegde discusses a mental model called “The map is not the territory” and how it can guide our decisions as a tester.
Testers shouldn’t be held as a gatekeepers for the final product. As such others should not be excludes either. Gregory Paciga explains this premise beautifully in this article.
➜ Read all curated stuff on Software Testing here.
One thing you as a tester or developer should never get into is this v/s that framework fight.
When it comes to automations and automated tests, there are plenty of things you can do. Here Brian Douglas describes 5 things as listed below.
Step up your security with CodeQL
Run npm test in your workflows to push the latest and greatest
Take a look at your build with automated visual tests
Use Lighthouse to make sure you’re not slowing your website down
Automate your releases (and release notes) with GitHub Actions
Code refactoring is good. It helps keep code clean and robust. But have you wondered if you might be just doing too much of it ? well, Jason Swett provides an interesting perspective.
UI tests and snapshot tests doesn’t replace each other but rather complements each other. Their focus is different and it might be confusing to understand when to write UI tests rather than screenshot tests and vice versa. Sergio does a very good job explaining the differences and how to use them.
See a practical example of how to organize automated postman collection execution inside Docker via newman CLI.
➜ Read all curated stuff on Software Testing Automation here.
It’s the end of the year and just like last year Naveen kumar has performance testing during the US holiday season and provides detailed guide on the same.
➜ Read all curated stuff on performance Testing here.
🎁 Bonus Content
OTHER INTERESTING STUFF
Will You Really Invest in Your People? by Steve Keating
This Is How Smart Risk-Takers Succeed by Larae Quy
LAST WEEK'S MOST READ
Postman Flows: 5 Example Flows (17 Clicks)
🛠️ Resources & Tools
dstp — Run common networking tests against your site, built with Go, available to install cross-platform.
jest-extended — Aims to add additional matchers (i.e. assertions) to Jest's defaults, making it easy to test everything.
📝 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.
📨 Send Me Your Articles, Tutorials, Tools!
😂 And Finally,
Keep Smiling and have a fun week.
👋 Reach Out
You can follow @thetestingkit to keep up-to-date on the community & fresh links to read.
Thanks so much for reading ,
Pritesh- Software Testing Notes