Welcome to the 271st issue!

Looking for a new software testing job?

Today, I want to highlight some recent advice from the community:

• What makes a Test Engineer's resume stand out?
• How to Build a Professional LinkedIn Profile as a QA Engineer? by Vladimir Josifoski

Happy job hunting and happy testing! 🙂

Dawid Dylowicz

Continuing the series on API testing, this time Aya Akl describes why it's crucial in a microservices architecture and explains how to approach it.

What would help companies and testers have a better hiring experience? Gabbi Trotter gives some good advice to those who are hiring.

Moreover, Yanina Kozlova shares interesting thoughts on How to Lead a QA Interview in the Age of AI.

How is it to be the only tester in the team, or even in the company? Mona M. Abd El-Rahman shares her experience and gives several valuable tips on how to handle such a situation.

Similarly, Callum Akehurst-Ryan describes a Quality Coaching Scenario: No testing happening and Wendy Erdheim-Poch advises on the Collaboration of QA in a Dev World.

This is a concise message from Jason Arbon stating that the most important part of a tester's job is to deliver value — regardless of whether it's achieved via tools or hands-on execution.

It's also crucial to Own Your Impact: Mastering Accomplishments in Software QA, as Sarat Ramineni explains.

If you're thinking of becoming a QA Manager, Brijendra Singh shares insights into being one and how the role differs from being an individual contributor.

Wondering how test doubles can help you test more effectively? Wahyu Hidayat explains with examples.

And if you want to see more of it in practice, Pradap Pandiyan demonstrates Mocking API Testing with JSON Server, Faker & JS in Gitlab CI.

Anton Oboleninov describes in detail their journey to setting up a test automation solution. Interestingly, they chose Selenium over Playwright since it better fits their use case.

Also, Chamila Ambahera wants us to remember that Good Test Automation Doesn't Start with Code.

Ebrar Tikit shares lots of helpful tips about testing Android applications on several levels. Examples included.

There are some interesting insights from Philip Riecks about testing Spring Boot apps built with Java. Philip has also previously shared the Top 5 Spring Boot Testing Myths.

Yet another story of building a test automation solution. This time, Ahmet Şimşek describes their approach, including tooling, tagging, CI and more.

Islam Taha describes the challenges with making their Playwright tests stable and what they learned from that. You can also catch up on the first part about Fighting False Alerts in Our Playwright Test Suite.

Writing UI tests for iOS apps? Chris Mash shows an intriguing implementation of a test failure observer that automatically halts the XCTest test suite after a certain number of tests fail.

Sometimes you may not want a single failure to stop your test execution. Mohamed Said Ibrahim gives a good overview of several ways to implement a soft assertion in Cypress.

It's a big day for Graphana k6! After nearly a decade, this popular performance testing tool has finally got its 1.0 version. Théo Crevon tells us more about the key updates.

Testing APIs with JavaScript? Eleonora Belova describes what makes PactumJS — an open-source test framework — so helpful.

Jose Alcérreca from the official Android Developers channel gives a high-level, 8-minute overview of test strategies for Android apps.

Jose has also recorded a short overview of Tools and patterns for scalable Android app testing.

In this short, 3-minute recording, Debbie O'Brien demonstrates how to easily use MCP and GitHub Copilot to implement Playwright tests.

And if you want to go deeper, check out Karthik K.K.'s 10-minute overview of Parallel Playwright Testing with Browser Use + Multi-LLM Support: The Future is Here.

VibeCon... 🤣

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