Welcome to the 101st issue!

Thanks for taking the time to ask me questions over the past two weeks.

I've just published the answers to the Ask Me Anything session.

I must admit I really enjoyed it and I'll be happy to do more of that in the future.

If you have any more questions or want to follow up on the answers, feel free to drop me a message on LinkedIn.

Happy testing! 😊

Dawid Dylowicz

And what happens? Kacper Witas and Anna Kalemba describe the benefits of such collaboration based on their experience.

Viktor Slavchev has a few solid points on what quality is and isn't, debunking some of the common misconceptions.

Moreover, Mike Harris explains how Improving quality creates a chain reaction.

Just like in Viktor's article, Peter Lupo did a similar breakdown of testing facts that are often overseen.

Payment service is one of the most critical components of many businesses. So how do you test it? Dmytro Lukianchuk shared an insightful article about it.

What testing is like? Jeff Nyman comes up with some sophisticated and accurate comparisons. It's good food for thought.

Here's a great article from Callum Akehurst-Ryan explaining what debrief is and why it's a very useful skill to have as a software tester, especially in exploratory testing.

Also, Simon Tomes gives a simple explanation of Exploratory Testing As An Alternative To Scripted Testing And "Try To Break It" Testing.

How do you measure the success of test automation? Zhimin Zhan has an interesting way of putting a number on this and showing a few examples.

Note: If you can't access the full article, simply open it in a private tab.

Blake Norrish asserts that good test automation doesn't equal automating all of the manual test cases. You might also be interested in the big discussion on Reddit that this article has sparked.

All test automation challenges are different. However, Benjamin Bischoff created handy guidelines that can help you decide on how to deal with a new automation task.

In this article, Artur Mishustin suggests what to do when you take over an existing test framework and how to navigate the refactoring.

GraphQL APIs are getting more popular, and so are the ways of testing them. Dalibor Kundrat describes how to use Postman's tool stack for that job.

Additionally, Dennis Martinez wrote a solid guide to Using Artillery to Load Test GraphQL APIs.

If you need to test flows including receiving or sending email, here's a handy overview of the popular free and commercial tools that you can use.

How do Selenium and Cypress compare? What are the key similarities and differences? Kishor Munot put together an informative comparison of these two popular tools.

Can you make JIRA work as a test management tool? Valeriy Lopakov proves you can! Here's an example of making it easier to store test cases, track implementation progress and see reports.

If you haven't read the Agile Testing book, you may want to check out Fatma Akın's article that explains the key concepts and principles.

Benjamin Bischoff demonstrates using make tool to simplify test runs with parametrised configuration.

Here's an interesting, 8-minute video by Nick Gilbert discussing why quality metrics are not easy to define and which ones you should and shouldn't use.

Devs, bugs and testers... 😂

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.

Dawid Dylowicz