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 61st 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.
Do you know that new Google Chrome 103 got released with a bunch of new features recently and one of the most notable features is the introduction of HTTP Status Code 103 that helps the browser decide what content to preload before the page has even started to arrive. But remember, Since this is a new HTTP status code, using it requires updates to your server. Naveen has written a nice introduction blog post about it with deep-dive into HTTP 103 status code with a quick demo.
Now, onto the this week’s links. I have lots of nice reads for you this week, let me know what your favorite is!
In some of previous issues, I have shared few links on how to manage being a single QA in a team. This week let me share this article by Paulo Oliveira where he shares 8 tips on what you can do to ensure great the quality, be able to deliver what is expected and much more…
You might have read many how to articles but have you ever stumble across How Not to article ? Well, I did this week. Seth Orell wrote a very nice article where he shares his experience on what he did wrong testing DynamoDB and warns us about few pitfalls for the same.
➜ Read all curated stuff on Software Testing here.
Code refactoring is a important part of the job regardless it’s development or testing. Lewis Prescott shares his experience of how code refactoring helps in overall maintenance and few tips to consider when you are refactoring your acceptance tests.
How to use the Factory design pattern to create browser instances: local and remote approach by Elias Nogueira
Very helpful guide with practical example and code organization diagram on how to execute your selenium test locally as well as remotely using factory design pattern.
In the last week’s Issue I shared a link about running JMeter distribution tests with Azure Load Testing. This week, read this post by Kherin Bundhoo on executing API tests with postman collections and Azure pipeline.
Mike Harris masterfully explains the importance of identifying states of functionality using State transition diagrams which could be very useful information and help you to know how changes in state take place and to identify tests that should be executed.
As Dennis Martinez rightly points out “you can't test absolutely everything in an application”. You need to prioritize and be smart about it. This article will be a great resource on how can you figure out what to focus on with so many options.
Gleb Bahmutov has put together this posts collecting all the tips for the working with Cypress v10.
➜ Read all curated stuff on Software Testing Automation here.
A job of the performance tester is to identify the memory leaks but as you move towards the performance engineering you should also know how to perform debug/troubleshoot the memory leaks as well. Take a look at this great article by Shimin Zhang explaining the same and also what things to consider when troubleshooting memory issues.
➜ Read all curated stuff on performance Testing here.
➜ Read all curated stuff on Security Testing here.
In this post, Sylvain Hamann shares his experience of performing accessibility testing and also shares some tips to test the accessibility of your web application or website better.
➜ Read all curated stuff on Accessibility Testing here.
MockRTC — Powerful and friendly WebRTC mock peer and proxy that lets you build automated tests for WebRTC traffic, simulate WebRTC errors in a reliable reproducible way, and more.
Cypress Chrome Recorder — Export Cypress tests from Google Chrome's DevTools recorder.
Jiffy Reader — Chrome extension that purports to 10X your reading speed with a simple brain hack. Demonstrated on the page and it does seem to work, though I can see why some might hate it.
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
- Nothing Works Until You Do
- 100+ Tools for an Easy Life 2022.
- Some tips on delivering assigned work on schedule.
⭐ LAST WEEK'S MOST READ
- As a Tester, What can I showcase except Bugs, Tests, and Bug Reports?
- Allure Report Hands-on Guide
- iOS security testing & reverse engineering guide
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.