Hello there! 👋
Welcome the 70th 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!
Here is something interesting I found last week.
Do you know that the term "bug" was first coined by Thomas Edison. It was to describe technical problems that occur during the process of innovation. But before it became popular in the area of computing, others also made use of the term, check out this fascinating article on the Origins of the Term “Bug” by Delvis Echeverria and enjoy the stories and cool infographics of the past.
P.S. Are you a 1x Engineer? Based on the qualities listed, I think we need more of those kinds of engineers.
Zalando Quality Engineering Journey—From Monolith to Microservices by Antoine Crask
This article shares an interesting case study of Zalando’s Quality Engineering transformation journey and the business and technology outcomes. I really enjoyed reading about integrating Quality Culture and the “open-source first” model. Thank you Antoine Crask for this very well written article.
Speaking of Microservices, David Tzemach also wrote about how to Test a System with Microservice Architecture.
"I would have found this bug with E2E tests" is a fallacy! by Maurício Aniche
Having E2E tests are important but should you solely relay on them? Maurício Aniche writes this article sharing his opinion on how E2E tests could become costly and might not give you the outcomes that you desire if you were to depend on them alone.
Some ways to get better at debugging by Julia Evans
Writing code is a one thing, but getting good at debugging is a whole another level of skillset to master. Julia Evans breaks down the entire thought process in five easy to get your head around categories and shares tips on how get better at debugging.
➜ Read all curated stuff on Software Testing here.
How do you automate tests through the GUI? by Markus Gärtner
This article makes a case against automating tests through the GUI (Desktop and Web) as long as possible. Markus Gärtner shares his views on the matter and few tips on what to do If you absolutely have to.
Additionally, there is a very interesting twitter thread going on by Stephan Kämper on automating things with GUI. you could have a have a look and share your views.
How Hashmap works Internally? by Sidharth Shukla
I’m sure you have used Hashmap religiously if you are working with Selenium Java for your automation needs. But would you like to know how they work internally? Take a look at this article by Sidharth Shukla and learn how Hashmap works in all of its glory.
Tips To Reduce Technical Debt by Oliver Karst
Whether it’s a development or testing, Technical Debt should be everyone’s concern. In this article, Oliver Karst shares few tips to minimize and reduce Technical Debt.
How to use stub with Cypress by Dawson
Wanna know what is stubbing and ways to implement them with Cypress? Then, take a look at this article by Dawson exploring how Cypress’s various methods such as
cy.stub(), cy.intercept(), cy.spy() and cy.clock() are used to create stubs for functions and API calls, spies and clocks with some practical code examples.
Customize iOS Simulator for Test Automation by Sunny Sun
In this article, Sunny Sun discusses how to create and configure an iOS simulator programmatically with the help of tools such as
➜ Read all curated stuff on Software Testing Automation.
Load testing with Artillery and Playwright by Katarzyna Kmiotek
Wanna learn how to set up Artillery performance tests using Playwright? Katarzyna Kmiotek did a nice POC on the same and has documented the process in this short and to the point article.
Correlation – The Hard Way in JMeter by NaveenKumar
What a fun experiment. Working with JMeter some times feels like a breeze. Want to store some value in a variable or extract some data from the element? Is it JSON? HTML? XML? any other? No Problem, JMeter has extractors for most of them.
But what if we didn’t have them? Read this article by Naveen and find out how the correlation is done manually with Groovy, JSoup and JSR223 Post processor.
➜ Read all curated stuff on Performance Testing.
Developers still struggling with security issues by Ben Dickson
Ben Dickson wrote a summary of the study by researchers at the University of Zurich, Switzerland on how developers perceive security during code reviews.
How to Prevent High Risk Authentication Coercion Vulnerabilities by Scott Fingar
Are you familiar with Windows New Technology LAN Manager? NTLM hashes are used for authentication, Take a peak at how PetitPotam and DFSCoerce could be used for the authentication coercion.
Scott also explains with example of Microsoft SQL Servers on how misconfigurations could also be dangers just as the technical vulnerabilities.
➜ Read all curated stuff on Security Testing.
🛠️ Resources & Tools
Gest — A sensible GraphQL testing tool to test your GraphQL schema locally and in the cloud.
Cherrybomb — A CLI tool that helps you avoid undefined user behavior by validating your API specifications and running API security tests.
Mock Service Worker — Mock API by intercepting requests on the network level. Seamlessly reuse the same mock definition for testing, development, and debugging.
📝 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
- Common Cypress Testing Pitfalls & How to Avoid Them
- Meet The New Automation Question, Same As The Old Automation Question
- How does xpath works internally?
😂 And Finally,
This guy killed it with this LinkedIn Resume. 🤣
Keep Smiling and have a fun week.
📨 Send Me Your Articles, Tutorials, Tools!
Wrote something? Send links via Direct Message on Twitter @thetestingkit (details here). If you have any suggestions for improvement or corrections, feel free to reply to this email.
Thanks to everyone for subscribing and reading!