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 58th 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.
Context is king. As such, when context changes about something, everything related to that also changes with it. Ben Dowen ponder on a one such question about When is a Tester not a Tester? and shares his views on testing, quality and responsibility.
On another note, Ben also compiled this nice list of blogs in software testing and development. Apart from this list, I also have a dedicated page for tester blogs, do check it out here. And if you have a blog on testing, you can add your profile here.
With that being said, I have lots of nice reads for you this week, reply to this email and let me know what your favorite is!
I’m always happy to see more con around game testing as the very nature of games is unpredictable hence testing them becomes a little bit hard. Adrian Gimate-Welsh and their QA team at TagWizz shares the twelve most common bugs encountered in testing.
Zhimin Zhan has written about simple, effective and should-have-been method to greatly increase software engineers’ productivity and morale.
A very thoughtful article by Michael Bolton on experiential testing (As Michael puts it ‘a positive replacement for one aspect of Manual testing’) and it’s usefulness, why should we care about it and stigma attached to it.
➜ Read all curated stuff on Software Testing here.
We talked a little bit about IoT test beds in previous issue. This week Vipin Jain describes how IoT testing approach is different from traditional testing and how it should be derived from the system and architecture involved.
Pour a cup of your favorite beverage and read everything you need to know about doing automation testing of mobile applications. This article by Niranjani Manoharan covers the introduction to mobile app components, choosing the right framework to automate iOS and Android Mobile Applications as well as performance testing of mobile apps.
Are you also getting tired of random and weird failures in your tests ? Imran Ali shares a quick and simple solution that can make your test framework more robust and your tests much more reliable.
In this post, Alekhya Chowdhury documents an approach on how we can use Jenkins to test GCP components meant to process events like Cloud Function, Cloud Run and Dataflow pipelines.
Whether you are a developer or tester, some of the basics knowledge of Linux is must for everyone. Here is a article by David Tzemach showing us few important Linux commands.
Here is post explaining the importance of learning DSLs when testing Rails apps. Jason Swett has also wrote couple of posts that can help you learn about DSLs which are already listed in this article.
A great detailed article by Akash Singh on how to configure jest to execute test cases on graphql typescript server inside docker.
➜ Read all curated stuff on Software Testing Automation here.
Never start your performance test with 100% of your projected load. Start small and increase the load gradually. In this short and to the point article Mohamed Tarek explains why we should start our execution gradually.
In this post, Pankaj Rawat shows us a very simple example of API load testing using NBomber C#. At the end, NBomber also generates HTML report which you can find from NBomber console result window.
➜ Read all curated stuff on performance Testing here.
If there was ever an easy guide to learning about CSRF attacks, this is the one. Zell Liew has written a complete and step-by-step article about CSRF Attacks and what you need to do in order to build secure web applications.
➜ Read all curated stuff on Security Testing here.
Wfuzz — makes it possible to evaluate web applications in a flexible way by injecting payloads (arbitrary inputs which can come from any data source) into any field of an HTTP request.
lemoncheesecake — is an end-to-end test framework for Python that brings trust around test results. It allows test developers to be very explicit about what their tests really do with logging, matchers, file attachments, etc..
Nbomber — Modern and flexible lightweight load testing framework for Pull and Push scenarios, designed to test any system regardless a protocol. With NBomber you can test any PULL or PUSH system (HTTP, WebSockets, GraphQl, gRPC, SQL Database, MongoDb, Redis etc).
OpenClove — Most sophisticated code coverage tool for Java and Groovy.
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
- Why Smart People Are So Easily Fooled
- Why cyber security can’t just say “no“
- 10 Time Management Tips That I Genuinely Use Everyday
⭐ LAST WEEK'S MOST READ
- How QA can lead a team to success
- Why it's Time to Stop Using Meaningless Test Values
- Become A Software Testing Detective – Part 2
Keep Smiling and have a fun week.
Thanks so much for reading ,
Pritesh- Software Testing Notes
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.