Welcome to the 229th issue!

It's hard to ignore the problem that CrowdStrike caused to the global tech.

That naturally started big discussions among the QA community:

1. This whole CrowdStrike bug
2. Guessing a lot of SDETs jobs are suddenly going to appear at CrowdStrike
3. Be fearless post the CrowdStrike defect

You can find a lot of different opinions, stories, rants, memes and pieces of advice in these big threads.

Happy testing! 🙂

Dawid Dylowicz  

Elevating Software Quality: The Enterprise Guide to Continuous Testing

Are you curious how leading enterprises consistently deliver quality digital experiences? It all comes down to a strategic approach to testing - one that supports continuous quality and provides rapid feedback across the SDLC. This is the ultimate guide to driving continuous software quality. Get the guide.

saucelabs.com  

Anybody heard of companies getting rid of QA and having integrated engineers do their own testing?

This is an interesting and relevant discussion — not only because a modern approach is to shift more testing responsibilities to developers but also because companies pay more attention to costs in the current economic environment.

At the same time, Priyanshu Shekhar wonders: Why QAs Are So Adamant?

reddit.com  

Making Progress on Regression Testing

This is a great, comprehensive overview by Michael Bolton of what to take into account when performing regression testing.

And if you haven't heard of the Rapid Software Testing approach, Winston Aleph Cruz Kasse had A quick look at the context-based methodology.

developsense.com  

Setting up Testing at an Engineering Org

Callum Akehurst-Ryan takes a deep dive into what it takes to establish testing and quality engineering practices.

Furthermore, Mark Shand's thoughts on Transforming Quality Culture are an excellent follow-up read.

cakehurstryan.com  

Software Quality and Developer Experience: Why testers should care about it

Part of the tester's role is to help others test better. Fernando Teixeira has several good tips on how we can improve the developer experience.

ministryoftesting.com  

7 rules to make TDD easier

Vladislav Ogir correctly recognises that common problems with tests, such as flakiness and long execution time, are not solved by tools but by following good practices.

Additionally, Josh Grant describes Enable, Execute, Expect as an alternative to Arrange, Act, Assert way of designing tests.

plainenglish.io  

How to improve your Test Automation

Hugh McCamphill gives good advice on separating workflows from interactions for better maintainability and readability of our tests.

And in a more broader scope, Jason Arbon shares insights into how AI Changed My Coding Style.

hughmccamphill.com  

UI Testing of Mobile apps at SafetyCulture

Altynay Shomanova describes the approach they've taken for mobile UI testing and what they learned from that.

Moreover, Neslihan Akdoğan Özüak provides details about Our Snapshot Test Journey.

medium.com  

What are your thoughts on the Test Pyramid? How does it work in reality?

The test pyramid (and other test shapes) seem to be a standard when it comes to test automation strategy. But is their implementation respected in actual codebases? Here's what the community observes.

reddit.com  

Why is it bad practice to write your programmatic tests like your manual tests?

One could think that automation is simply taking manual tests and reproducing them one-to-one in code. But, usually, that's not the best way to do it and Maaret Pyhäjärvi explains why.

blogspot.com  

A Simple and Effective E2E Test Architecture with Playwright and TypeScript

In this helpful example, Denis Skvortsov shows a good way of structuring your Playwright test automation project

And with the rising popularity of the tool, some are asking: Should I fight for Playwright?

medium.com  

Building a Robust Automated Test Suite with Behave and Selenium

If you're looking for an example of implementing Selenium tests in the BDD fashion, Rajesh Vinayagam wrote a decent guide on doing it with Behave in Python.

Similarly, Pepqy Satria Dharma Mumpuni demonstrates How to design Cypress Framework with the BDD approach.

medium.com  

Test Tools vs. Test Libraries vs. Test Frameworks

Wondering what the difference between these three notions is? Arek Frankowski explained it well.

medium.com  

Why "page.goto()" is slowing down your Playwright tests

Want to speed up your Playwright tests? Stefan Judis has a great tip, which you can learn from this 9-minute video.

checklyhq.com  

AI Generates And Runs Automation Code: LaVague.ai

In this intriguing 35-minute recording, Daniel Huynh and Paul Palmieri joined Nikolay Advolodkin for a talk about LaVague — an open-source Large Action Models framework to build AI Web Agents.

On the other hand, Pramod Dutta shares some advice on How Not to Get Replaced by AI: Strategies for QA Professionals.

youtube.com  

Playwright POM (Page Object Model)

If you're looking for a thorough guide on implementing Page Object Model in Playwright, this one-hour overview by Alex Khvastovich should get you covered.

Similarly, Jarad Saunders explains Page Object Model in Playwright C# in 16 minutes.

youtube.com  

The MOST visible bug... 😅

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