> ## Content Index > Fetch the complete content index at: https://softwaretestingweekly.com/llms.txt > Use this file to discover other available public pages before exploring further. # Issue #215 - URL: https://softwaretestingweekly.com/issues/215/ - Published: 2024-04-14T11:00:00.000Z - Updated: 2026-06-10T13:18:39.000Z - Description: Lessons Learned From 20 Years Of Software Testing 💡 - Author: Dawid Dylowicz | Comment | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Welcome to the **215th** issue!This is one of the highlights I read this week:[Lessons Learned From 20 Years Of Software Testing](https://www.ministryoftesting.com/articles/lessons-learned-from-20-years-of-software-testing?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215).I really liked practical advice and unconventional wisdom that [Ady Stokes](https://www.linkedin.com/in/a11yadystokes/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) shared here.I'm sure you'll find it helpful as well.Happy testing! 🙂*[Dawid Dylowicz](https://linkedin.com/in/dawid-dylowicz/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215)* | | | | Sponsored [TimeShiftX — Travel in Time, Test with Ease](https://www.vornexinc.com/?utm%5Fsource=STW&utm%5Fmedium=newsletter24)[TimeShiftX](https://www.vornexinc.com/?utm%5Fsource=STW&utm%5Fmedium=newsletter24) lets you time travel your software to test date and time-sensitive functionality and code such as year-end, daylight savings, and billing. Employ instant time shifting inside Active Directory & Kerberos without code or system clock changes and removing all pain points. [Check it out](https://www.vornexinc.com/?utm%5Fsource=STW&utm%5Fmedium=newsletter24)![vornexinc.com](https://www.vornexinc.com/?utm%5Fsource=STW&utm%5Fmedium=newsletter24) | | | | NEWS | | [Accessibility Testing: Creating a World Without Walls](https://blog.qatestlab.com/2024/04/03/accessibility-testing-creating-a-world-without-walls/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215)With accessibility becoming more important, it's good to see guides such as this one by [Mariia Furta](https://www.linkedin.com/in/mariia-furta-779754236/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) describing the solutions we can use to test for it on mobile and desktop platforms.Similarly, [Andreea Draniceanu](https://www.linkedin.com/in/%F0%9F%92%BBandreea-d-2ab81853/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) wrote a short overview of [Accessibility Testing for Mobile Apps](https://www.testim.io/blog/accessibility-testing-for-mobile-apps/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215).[blog.qatestlab.com](https://blog.qatestlab.com/2024/04/03/accessibility-testing-creating-a-world-without-walls/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) | | ["Agile" is not sacred](https://failfastmoveon.blogspot.com/2024/04/agile-is-not-sacred.html?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215)Most tech companies practice Agile but here are a few reminders from [Michael Küsters](https://www.linkedin.com/in/michaelkuesters/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) on what to avoid.Moreover, [Joep Schuurkes](https://www.linkedin.com/in/joepschuurkes/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) brings up some comparisons from the [Extreme Ownership](https://www.goodreads.com/book/show/23848190-extreme-ownership?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) book to explain [The difference between a dead and an alive Agile Manifesto](https://smallsheds.garden/blog/2024/the-difference-between-a-dead-and-an-alive-agile-manifesto/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215).[failfastmoveon.blogspot.com](https://failfastmoveon.blogspot.com/2024/04/agile-is-not-sacred.html?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) | | [Android Interruption Testing](https://medium.com/@begunova/android-interruption-testing-017f6221146c?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215)Is your Android app prepared for handling unexpected phone calls, missing internet connection or switching to another app? [Lana Begunova](https://www.linkedin.com/in/lanabegunova/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) advises how to test for such scenarios.[medium.com](https://medium.com/@begunova/android-interruption-testing-017f6221146c?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) | | [Coding with Quality in Mind: 5 Takeaways from My Journey from QA to Software Developer](https://medium.com/@oleg.mais.box/coding-with-quality-in-mind-5-takeaways-from-my-journey-from-qa-to-software-developer-860aefd73af2?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215)*"You may leave QA, but QA will not leave you"*. Or at least that's my impression of the insights that [Aleh Maisevich](https://www.linkedin.com/in/aleh-maisevich-35a93ba0/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) shared after moving to development.[medium.com](https://medium.com/@oleg.mais.box/coding-with-quality-in-mind-5-takeaways-from-my-journey-from-qa-to-software-developer-860aefd73af2?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) | | [Is the QA team responsible for prod bugs?](https://www.reddit.com/r/QualityAssurance/comments/1bx6h8h/is%5Fqa%5Fteam%5Fresponsible%5Ffor%5Fprod%5Fbugs/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215)It's easy to point fingers at others and blame them for bugs. But that's not the right way, and here's what testers think should be done instead.Also, what if [Devs are doing all the testing](https://www.reddit.com/r/QualityAssurance/comments/1bvx1vn/devs%5Fdoing%5Fall%5Fthe%5Ftesting%5Fcan%5Fanyone%5Frelate/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215)?[reddit.com](https://www.reddit.com/r/QualityAssurance/comments/1bx6h8h/is%5Fqa%5Fteam%5Fresponsible%5Ffor%5Fprod%5Fbugs/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) | | | | AUTOMATION | | [How to Identify, Fix, and Prevent Flaky Tests](https://www.testrail.com/blog/flaky-tests/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215)If you want to know how to deal with flaky tests in general, [Deepika Kale](https://www.linkedin.com/in/deepika-kale/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) wrote a good, high-level overview.And [Wayne Roseberry](https://www.linkedin.com/in/wayneroseberry/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) suggests that sometimes you need to [Think Like A Tester And Go Beyond The Code](https://waynemroseberry.github.io/2024/04/05/Think-like-a-tester-and-go-beyond-the-code.html?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215).[testrail.com](https://www.testrail.com/blog/flaky-tests/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) | | [Prefer Narrow Assertions in Unit Tests](https://testing.googleblog.com/2024/04/prefer-narrow-assertions-in-unit-tests.html?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215)[Kai Kent](https://www.linkedin.com/in/kai-kent-695821106/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) from Google shares a helpful tip on making unit test assertions more focused. This can be applied to other types of tests, too.And what if you need to debug a test failure? [Konstantin Sakhchinskiy](https://www.linkedin.com/in/konstantin-sakhchinskiy/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) shows [How to Save All App's Debug Logs and Write Your Own Logs](https://dzone.com/articles/writing-your-own-logs?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215).[testing.googleblog.com](https://testing.googleblog.com/2024/04/prefer-narrow-assertions-in-unit-tests.html?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) | | [Running all automated tests against every commit](https://new.reddit.com/r/QualityAssurance/comments/1bzd7vd/running%5Fall%5Fautomated%5Ftests%5Fagainst%5Fevery%5Fcommit/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215)Is it a good idea or not? While the right answer depends on the context, there are some good suggestions from other testers.Furthermore, [Irfan Mujagić](https://www.linkedin.com/in/irfan-mujagi%C4%87-618435206/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) explores [The ROI of UI Automation Testing: Effort vs. Impact](https://www.thegreenreport.blog/articles/the-roi-of-ui-automation-testing-effort-vs-impact/the-roi-of-ui-automation-testing-effort-vs-impact.html?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215).[new.reddit.com](https://new.reddit.com/r/QualityAssurance/comments/1bzd7vd/running%5Fall%5Fautomated%5Ftests%5Fagainst%5Fevery%5Fcommit/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) | | [Shifting UI tests to the far left (part 2)](https://medium.com/@ge.sotiropoulos/shifting-ui-tests-to-the-far-left-part-2-a8a5c8b71df1?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215)Following [the first part](https://softwaretestingweekly.com/issues/214?m=web&utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215#IRdgXXm) mentioned last week, [Georgios Sotiropoulos](https://www.linkedin.com/in/gesotiropoulos/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) shows how to implement UI tests before coding and describes the benefits it may yield.In relation to that, [Chamila Ambahera](https://www.linkedin.com/in/ambahera/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) advises on choosing the [Tool Stack for The Shift Left Testing Approach](https://ambahera.medium.com/tool-stack-for-the-shift-left-testing-approach-d10db80bded3?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215).[medium.com](https://medium.com/@ge.sotiropoulos/shifting-ui-tests-to-the-far-left-part-2-a8a5c8b71df1?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) | | [SOLID Principles for Testers: The Single Responsibility Principle](https://thinkingtester.com/solid-principles-for-testers-the-single-responsibility-principle/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215)If you liked the previous series of articles by [Kristin Jackvony](https://www.linkedin.com/in/kristinjackvony/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215), you'll likely enjoy this one about the SOLID principles in test automation as well.Moreover, [Smruti Sourav Sahoo](https://www.linkedin.com/in/smruti-sourav-2000/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) shows a good example of [Building Robust Test Automation Framework: Factory Design Pattern](https://smrutisouravsahoo06.medium.com/building-robust-test-automation-framework-factory-design-pattern-9e6018ac5889?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215).[thinkingtester.com](https://thinkingtester.com/solid-principles-for-testers-the-single-responsibility-principle/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) | | | | TOOLS | | [How to Perform Load, Performance Testing Using the Gatling Recorder](https://hardikchotaliya.hashnode.dev/load-performance-testing-gatling-recorder-guide?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215)Considering using [Gatling](https://gatling.io/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) for load testing? [Hardik Chotaliya](https://www.linkedin.com/in/hardikchotaliya/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) demonstrates how to benefit from its recorder for easy test creation.[hardikchotaliya.hashnode.dev](https://hardikchotaliya.hashnode.dev/load-performance-testing-gatling-recorder-guide?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) | | [Important Git commands that every QA engineer should learn](https://medium.com/@bhushantbn/important-git-commands-that-every-qa-engineer-should-learn-fdd511937bbb?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215)Whether you want to learn Git from scratch or just practice the basics, [Bhushan Trivedi](https://www.linkedin.com/in/bhushan-trivedi-12822558/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) created a clear guide with examples for the most used commands.[medium.com](https://medium.com/@bhushantbn/important-git-commands-that-every-qa-engineer-should-learn-fdd511937bbb?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) | | [Next-Level API Testing: Unlocking Automated Regression with Replay Tests](https://medium.com/@k.shefer/next-level-api-testing-unlocking-automated-regression-with-replay-tests-4395a5030bec?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215)[Konstantin Shefer](https://medium.com/@k.shefer?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) shows how to use the replay feature of [Vedro](https://vedro.io/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) — an open-source Python tool for API testing.Also, [Gil Zilberfeld](https://www.linkedin.com/in/gilzilberfeld/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) advises on [Better API Testing](https://www.everydayunittesting.com/2024/04/better-api-testing-a-boxing-match.html?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) by trying to understand more about the underlying system.[medium.com](https://medium.com/@k.shefer/next-level-api-testing-unlocking-automated-regression-with-replay-tests-4395a5030bec?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) | | [Playwright tips and tricks #3](https://blog.martioli.com/playwright-tips-and-tricks-3/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215)In the third part of the popular series, [Adrian Maciuc](https://www.linkedin.com/in/adrian-maciuc/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) shares even more handy tips for testing with [Playwright](https://playwright.dev/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215).Also, [Vinicius Gabriel Cabral Paulino](https://www.linkedin.com/in/vgcp/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) wrote a great guide explaining how to address [Playwright Visual Tests and the "Environment Flakiness"](https://vgcpaulino.medium.com/playwright-visual-tests-and-the-environment-flakiness-6fae79a5e4dd?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215).[blog.martioli.com](https://blog.martioli.com/playwright-tips-and-tricks-3/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) | | [Testing AI — How to create Automated Prompt Testing With Playwright](https://www.thequalityduck.co.uk/testing-ai-how-to-create-automated-prompt-testing-with-playwright/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215)Wondering how to test the output of LLM-based apps? [Stuart Thomas](https://www.linkedin.com/in/stuart-thomas-quality-engineer/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) shows a few ways of achieving that with [Playwright](https://playwright.dev/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) and [TruLens](https://www.thequalityduck.co.uk/testing-ai-how-to-assess-llm-quality-with-trulens/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215).Additionally, [Linda Benboudiaf](https://www.linkedin.com/in/lindabenboudiaf/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) wrote a helpful guide to [Mastering Prompt Engineering: Elevating QA Testing Automation with Contextual Examples](https://medium.com/@lbenboudiaf/mastering-prompt-engineering-elevating-qa-testing-automation-with-contextual-examples-5a072d3b7807?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215).[thequalityduck.co.uk](https://www.thequalityduck.co.uk/testing-ai-how-to-create-automated-prompt-testing-with-playwright/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) | | | | BOOKS | | [Looking back at Agile Testing, 15 years on](https://agiletester.ca/looking-back-at-agile-testing-15-years-on/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215)With the famous [Agile Testing](https://www.goodreads.com/en/book/show/5341009?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) book turning 15 this year, [Lisa Crispin](https://www.linkedin.com/in/lisacrispin/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) and [Janet Gregory](https://www.linkedin.com/in/janetgregory/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) look back on what has changed since and what they would have included in the book today.[agiletester.ca](https://agiletester.ca/looking-back-at-agile-testing-15-years-on/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) | | | | And… | | [Six stages of debugging...](https://www.reddit.com/r/ProgrammerHumor/comments/1c0mwuv/notmymachine/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215) 😂 | | | | 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](https://buymeacoffee.com/softwaretestingweekly?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215).*[Dawid Dylowicz](https://linkedin.com/in/dawid-dylowicz/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F215)* |