Testing skills every QA Engineer and Developer should master
How does programming experience help you be a better Quality Assurance Engineer? How much testing should a QA do? Read an interview with Software Programmers and QA Engineers at Brainhub about what every developer should know about testing the code.
Making the monolith testable
How should you test a monolith? Kevin Coulombe suggests checking the test coverage and using The Testing Trophy strategy.
Notes on Testing Notes
Taking notes while you test is a powerful practice. James Thomas shares a few tips from his experience on how to do it well.
In relation to that, Bob Salmon brought up some interesting Analogies and objectives for testing, explaining why testing is about information hunting and more.
Quality Score @ MiQ
Vishal Lad shows an example of calculating a quality score for services and applications using various signals: from test coverage to bug counts.
Testing a data pipeline
Bob Salmon shares with us three handy techniques to test an ETL data pipeline that focus on the content, the consistency and the output.
The Ideal Tester-Developer Ratio
While there might not be one that works in every case, Kristin Jackvony describes the pros and cons of various possible ratios. Personally, I also consider the 1:1 tester per product manager ratio as an option.
Similarly, someone asked on Reddit: How to divide work between 2 testers in the same team?.
This Is How To Start In Quality Engineering (Methods)
Antoine Craske shares a few helpful practices that can help you build quality in your software development life cycle.
Moreover, Antoine also wrote about Setting Goals with OKRs In Quality Engineering.
Move from Manual to Automation Test role: guide based on real experience
If you're planning to move to test automation, Olesia Martushkanova has some tips and lessons learned on how to successfully go through that journey.
Serverless Testing Pyramid
"If you want to use serverless technologies, but still insist on testing everything together locally, then your mindset isn't there yet." — prozz
Good advice for testing apps in the serverless architecture.
Test your code E2E without Internet
Vaibhav Saraswat faced the interesting challenge of making his tests run offline and sharing what they learned from that.
Why test coverage targets backfire
Michael Küsters uses insightful examples to show why relying solely on test coverage metrics might not tell us the full story about the quality of our product.
📢 A New Podcast — How to Test Microservices with API Contracts
Contract testing makes testing in microservices easier, so why not start today! In this podcast series, we chat to expert guests about the challenges they face in testing microservices and much more. Listen now!
Easy Solutions to WebDriver Testing Problems
Ever run into problems using WebDriver? Cagri Ataseven has some good advice on how to solve the common ones.
Improving Cypress logging with the decorator pattern
If you want to get more visibility of what's going on in your Cypress tests, here's a simple tip from Boris Arapovic on using the decorator pattern to improve your logs.
In addition to that, Ginta Purina wrote about Useful Information QA Engineers Can Find in Application Logs.
Top docker lifehacks for QA
In this cheat sheet, Alexey Anisimov shares a few clever tips that can make your testing with Docker easier.
10 Books Every Senior Engineer Should Read
While this handy list of books by Tomas Fernandez is generally targeting software engineers rather than testers, you may still find some relevant reads to your role.
Thanks for reading!
If you like this newsletter and it helps you become a better tester, you can say thanks and buy me a coffee.
PS. I'll be transferring every donation to Nasz Wybór Foundation which supports Ukrainian refugees in Poland. 🇺🇦 🙏
Welcome to the 119th issue!
Hope you had a good week and you're off to a well-deserved break.
But before you go, I want to share with you three sets of short tips for software testers that I found valuable this week:
Happy testing!Dawid Dylowicz