Welcome to the 87th issue!

You might be well aware of Agile already, but have you heard of Agile 2?

20 years after the original Agile Manifesto, Cliff Berg, Lisa Cooney and many other contributors decided that it's time for a new iteration, tailored for modern times.

The most intriguing part is of course the Values and Principles. It looks interesting and I wonder how much adoption and practical use it will bring in the future.

PS. Thanks Justas Laužadis for letting me know about it.

Happy testing!

Dawid Dylowicz

It's hard to deny the usefulness of any of the soft skills that Marine Lacourie listed here. All of them can be very helpful in the software testing career.

Additionally, Yusra Marikkar asks about one more skill: Do you "check if it works"?.

Thinking of taking on a leadership role? Toyer Mamoojee wrote a great article including many tips on what you can do to make the transition happen.

We all know the importance of a healthy culture of quality. But do you know what it means to every role in your company? Pradeep Soundararajan wrote an excellent piece explaining just that.

Marie Drake raises a few good points on why accessibility testing is so important and how it can be implemented early in the development process.

On the other hand, Edzo Botjes warns about The shift left fallacy and why we need to be careful not to overdo it.

Luciana Mores Bernardi shares some valuable thoughts on why analytics can help you better understand your users and which metrics you can use to improve quality.

Olga Beregnaya wrote a nice guide to creating a Testing Scope that, in contrast to a Test Plan, mostly focuses on the "what" of testing.

Speaking of that, Do you write and follow a "Test Plan"?. I was surprised by the results of this poll!

Eldad Uzman explains what Page Object Model is about and why its shortcomings may outweigh the benefits.

Joe Colantonio has some great tips on what you should NOT do while automating your tests. I couldn't agree more!

If you're wondering whether you should keep using the existing test framework or invest in a new solution, Anton Angelov has some pieces of advice for you.

There's nothing better than learning from a working example. Dmitrii Makarenko wrote an amazing, two-part guide explaining the details of the test framework they use at Bumble.

And here you can read the Part 2: preconditions, elements verification and independent steps.

Curtis Carter describes a few interesting concepts, such as Component Object, Active Flows, Conditional Flows, using a test automation solution for web in C# with Selenium as an example.

In this short but insightful list of pros and cons, Ravi Shankar Pandey explains when it's worth focusing on API testing and when on front-end testing.

Also, Lizi Boros gives a hint about using the Automated & manual QA as one integrated process.

Martin Thoma wrote another solid overview of an API testing tool. Last week it was about HTTPie, and this time he describes Insomnia.

Similarly, Pricilla Bilavendran and Priyanka Brahmane describe how to write API assertions with examples in two different tools: Karate and Postman.

Screen capture is one of the handiest tools for any tester. Someone is looking for one on Reddit and people suggested plenty of tools in the answers.

XPath is widely used in web test automation, so it's good to know how to properly use it. Sajitha Pathirana shares some handy practices.

James Thomas did a great job listing out a lot of powerful quotes from the Systemantics: How Systems Work and Especially How They Fail book.

This is a brilliant presentation from Alan Page about what a culture of quality is and how you can lead the change in the team with some practical examples.

Yeah, we've all been there... 😂

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