Welcome to the 249th issue!

The results of the State of Frontend 2024 survey are here!

What's there for testers?

• TypeScript has essentially become the go-to language,
• Developer (and testing) experience is becoming even more important,
• AI is believed to enhance test coverage while making testing more efficient,
• Cypress is still slightly more popular than Playwright. Selenium isn't mentioned.

And on top of that, I'm positively surprised that developers are involved in testing in 87% of cases. That's impressive.

You can also read an insightful overview of Frontend Trends: What to Expect in 2025 based on that report, compiled by Andrzej Wysoczański.

Happy testing! 🙂

Dawid Dylowicz

It's hard to disagree with Gaurav Singh's point of view. Good communication skills are especially important in the testing role.

Joining a new team and wondering how to kick off testing processes? There are several detailed pieces of advice from the testing community on what to do.

Furthermore, Katja Obring shares a perspective of The Solo Tester's Dilemma: When Enterprise Metrics Don't Fit.

Developers and testers can learn a lot from each other. It's an excellent take by Filip Hric on the importance of looking from a different perspective.

Alan Page shares a few good thoughts.

In relation to that, Mike Harris suggests that Interpreting 'quality' in more than one way helps me uncover issues.

Although the approaches to shift-left or in-sprint testing may vary, Jayson Labarrete provides a decent example.

Pull request reviews are one of the quality gates. But is there a way to do it differently? Gil Zilberfeld suggests pair programming as a possible substitution.

If you work on testing Android apps, Alexey Alter-Pesotskiy has a few helpful tips on making parallel test execution easier to handle.

Are your tests flaky? They can fail for various reasons and Dennis Martinez explains several ways of solving them.

Also, Stefan Dirnstorfer says it may be worth doing something about Failing with grace: A tester's guide to error culture.

Rafael Miguel makes a few good points about the benefits of practising Test-Driven Development, highlighting that it goes far beyond just making the code work.

This. among other things, is also emphasised by Team Merlin in their take on different Software Testability measures.

Postman is a popular API testing tool, but given its focus on commercialisation, some people are looking for more lightweight and open-source alternatives. Here are some suggestions.

Inspired by Playwright's powerful toHaveText() assertion, Gleb Bahmutov shows how to achieve a similar behaviour with Cypress.

Want to improve test observability? Gaurav Singh demonstrates how to set up and use the open-source tool ReportPortal for insightful test-related metrics.

If you're looking into validating your web app behaviour in failure scenarios, Balaji Kumarasamy shows a handy guide to validating that with Playwright tests.

Also, Rinkesh Patel shares a concise Recipe for managing Playwright tests for different deployment environments.

AI development is not stopping. In 17 minutes, Karthik K.K shows a live example of automating simple web app tests using just a few prompts.

Similarly, Beth Marshall explored using a couple of AI tools to Create Test Framework in Under Two Hours.

Following the mid-year update on the state of the QA job market, Alex Khvastovich does another great, comprehensive analysis.

Sometimes automation pays off... 😂

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