Issue #239
Quality Engineering Strategy 🚀
|
|||
|
Welcome to the 239th issue! Today, I want to highlight this — Quality Engineering for CEOs: Exploring QE Strategy. It's the third part of the brilliant, pragmatic and practical series on Quality Engineering. This time, it's about setting the strategy. And it's not something you'd see very often. Why? Because it's based on Steve Semelsberger's experience working with many executives on defining and improving the quality of their products. So enjoy the read and happy testing! 🙂 |
|||
|
|
|||
|
|||
|
|
|||
|
|||
|
I am tired of AI (in testing and not only) Bas Dijkstra shares a sobering opinion on the current state of AI and its applications in testing and other areas. |
|||
|
Implementing Test Pyramid: Journey of Shifting Left and Scaling Quality Krishna Chaitanya describes the challenges of implementing a test pyramid and advises on how to overcome them. |
|||
|
Is starting accidentally in QA a thing? Yes! And a lot of testers confirm it in this Reddit thread. As someone accurately pointed out — "You don't find QA. It's QA that finds you.". |
|||
|
The Two Pillars of Modern QA: From Error Prevention to Error Detection Mohsen Nasiri points out how the tester's role has evolved and what it takes to be good at it nowadays. Additionally, Kamal Pokharel shares about the challenges with the Zero Issue Mindset in Software QA. |
|||
|
|
|||
|
|||
|
Creating self-healing automated tests with AI and Playwright Shray Sharma describes an interesting solution of using LLM-based AI to run, generate and fix Playwright, Cypress or Selenium tests. |
|||
|
How to Learn Generative AI for QA Automation And if you're curious about how you can leverage AI for test automation in general, Pramod Dutta. wrote a handy overview. |
|||
|
SDET: Saga about test data management for your automation tests Kostiantyn Teltov shares tons of advice on creating test data by describing and demonstrating different approaches and highlighting their pros and cons. In relation to that, you might be interested in Poya Shad's new invention: I built a Fake Log Generator. |
|||
|
The Art of Pitching Automation Improvements in a QA Team Want to get a buy-in for changes to a test automation project? Irfan Mujagić advises on how to prepare and achieve that. |
|||
|
|
|||
|
|||
|
|
|||
|
|||
|
API Mocking using Playwright Bakkappa N neatly describes three possible ways of mocking APIs in Playwright tests with examples. Additionally, Mohammad Faisal Khatri explains How to test POST requests in Playwright. |
|||
|
Cypress Automation with SOLID Principles: A Simple Guide to Clean, Scalable Tests Wondering how you can apply SOLID principles in practice? Updesh Kumar Singh shows examples of Cypress tests. Also, Sebastian Clavijo Suero wrote an interesting article about Dynamic Tests in Cypress: To Loop or Not To Loop. |
|||
|
How to parameterize Playwright projects Stefan Judis put together an insightful guide on using options to configure fixtures, page object models, and tests in Playwright. Furthermore, Priyanshu Shekhar helps you get An In-Depth Understanding of getByRole in Playwright. |
|||
|
Playwright Productivity Hack: How --only-changed Can Save Your Day With the latest release, Playwright introduced a new feature Similarly, Butch Mayhew used the same feature to find out: Is it possible to run only Playwright Tests that changed in GitHub actions on a pull request? |
|||
|
Why we switched from Cypress to Playwright Varun Sriram shared an honest and detailed story on how they initially started their test automation with Cypress and why they eventually moved to Playwright. |
|||
|
|
|||
|
|||
|
A great resource for leaders in test and quality — A review of "Learning to Lead, Leading to Learn" Mike Harris shared a short review and recommendation of the book from Toyota's former leader — Learning to Lead, Leading to Learn. |
|||
|
|
|||
|
|||
|
|
|||
|
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. |