> ## 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 #322 - URL: https://softwaretestingweekly.com/issues/322/ - Published: 2026-08-10T08:00:32.000Z - Updated: 2026-08-10T08:22:56.000Z - Description: Playwright Quest — learn through playing! 👾 - Author: Dawid Dylowicz | Comment | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Welcome to the **322nd** issue!Something different this week.Meet [Playwright Quest](https://www.playwrightquest.com/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) — an online game that helps you learn Playwright, step-by-step.I had fun playing it, and it works whether you're getting started or want to test your knowledge.It's also been [warmly welcomed](https://www.reddit.com/r/QualityAssurance/comments/1ve7a7o/i%5Fbuilt%5Fa%5Fgame%5Fto%5Flearn%5Fplaywright%5Ftypescript/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) by the testing community on Reddit.So, happy learning! 🙂*[Dawid Dylowicz](https://www.linkedin.com/in/dawid-dylowicz/?ref=softwaretestingweekly.com)* | | | | Sponsored [Filip Hric on Escaping the Test Maintenance Loop with AI Agents](https://www.browserstack.com/webinars/loop-of-test-maintenance?utm%5Fsource=newsletter&utm%5Fmedium=PR&utm%5Fplatform=&utm%5Fcontent=digitalevent&utm%5Fcampaign=WBN-AI-in-Testing-19th-August-26&utm%5Fcampaigncode=701OW00000vjAVSYA2&utm%5Fterm=software-testing-weekly-19/08)Tired of losing half your day to tests that broke because the UI changed? Filip Hric of Qodo joins BrowserStack's Shubham Zapate to discuss where AI agents actually earn their keep:Keeping UI changes from breaking your tests with self-healing locatorsCatching visual bugs that functional tests never seeRunning your test suite across thousands of real devicesVirtual, 19 August, 6:00 PM CEST — [Register here](https://www.browserstack.com/webinars/loop-of-test-maintenance?utm%5Fsource=newsletter&utm%5Fmedium=PR&utm%5Fplatform=&utm%5Fcontent=digitalevent&utm%5Fcampaign=WBN-AI-in-Testing-19th-August-26&utm%5Fcampaigncode=701OW00000vjAVSYA2&utm%5Fterm=software-testing-weekly-19/08).[browserstack.com](https://www.browserstack.com/webinars/loop-of-test-maintenance?utm%5Fsource=newsletter&utm%5Fmedium=PR&utm%5Fplatform=&utm%5Fcontent=digitalevent&utm%5Fcampaign=WBN-AI-in-Testing-19th-August-26&utm%5Fcampaigncode=701OW00000vjAVSYA2&utm%5Fterm=software-testing-weekly-19/08) | | [Reach **9,206** software testers with a sponsored link →](https://softwaretestingweekly.com/sponsorship) | | | | News | | [Building AI Agents Is Mostly a Quality Engineering Problem](https://medium.com/htx-s-s-coe/building-ai-agents-is-mostly-a-quality-engineering-problem-595297a56104?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322)An interesting point of view from [Kek Wee Tan](https://www.linkedin.com/in/kwt0968/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) who finds out that most bugs aren't in the model but in the instructions. For example, a guardrail that fixes one problem can potentially create another.Moreover, [Janna Loeffler](https://www.linkedin.com/in/jannaloeffler/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) points out why [QA should build agents that make everyone else's work safer](https://www.linkedin.com/feed/update/urn:li:activity:7482784742338318336/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322).[medium.com](https://medium.com/htx-s-s-coe/building-ai-agents-is-mostly-a-quality-engineering-problem-595297a56104?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) | | [Dark patterns: Downsizing QA teams in the age of AI](https://newsletter.automationhacks.io/p/dark-patterns-downsizing-qa-teams-in-the-age-of-ai?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322)Are QA teams being quietly downsized because of AI? [Gaurav Singh](https://www.linkedin.com/in/automationhacks/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) writes an honest, personal take on what's happening, why leaders fall for it and how testers should respond.Also, [Jaclyn Leigh](https://www.linkedin.com/in/jaclynlilly/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) has a good message to testers: [You're Probably Doing More Than "Manual Testing"](https://insitepeek.net/blog/youre-probably-doing-more-than-manual-testing/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322).[newsletter.automationhacks.io](https://newsletter.automationhacks.io/p/dark-patterns-downsizing-qa-teams-in-the-age-of-ai?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) | | [Is manual testing dead?](https://medium.com/@jamin.chaput/is-manual-testing-dead-80f488cbc6ea?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322)While automation (and AI) can cover most regression paths, [Jamin Chaput](https://www.linkedin.com/in/jamin-chaput/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) says they'll never replace the experience and empathy a skilled manual tester brings to the table.In relation to that, you can also check out two insightful Reddit threads: [Do you still run manual tests? To what extent?](https://www.reddit.com/r/QualityAssurance/comments/1v8cmfb/do%5Fyou%5Fstill%5Fdo%5Frun%5Fmanual%5Ftests%5Fto%5Fwhat%5Fextent/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) and [Using AI for manual testing](https://www.reddit.com/r/softwaretesting/comments/1v8pnu7/ai%5Ffor%5Fmanual%5Ftesting/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322).[medium.com](https://medium.com/@jamin.chaput/is-manual-testing-dead-80f488cbc6ea?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) | | [The Real Bottleneck in AI-Native Quality Is Trust!](https://danashby.co.uk/2026/07/29/the-real-bottleneck-in-ai-native-quality-is-trust/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322)[Dan Ashby](https://www.linkedin.com/in/dan-ashby/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) looks at why AI testing tools get adopted but aren't always used, and what engineering leaders can do to help their teams build enough trust to change how they work.At the same time, [Janet Gregory](https://www.linkedin.com/in/janetgregory/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) outlines who's really in charge of [AI Accountability](https://agiletestingfellow.com/blog/post/ai-accountability?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322).[danashby.co.uk](https://danashby.co.uk/2026/07/29/the-real-bottleneck-in-ai-native-quality-is-trust/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) | | [Understand exploratory testing, and unlock its true value](https://www.thequalityduck.co.uk/understand-exploratory-testing-and-unlock-its-true-value/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322)Want to know why exploratory testing is important? [Stuart Thomas](https://www.linkedin.com/in/stuart-thomas-engineering-leadership/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) gives a thorough, practical breakdown, including how to run it alongside AI systems.Additionally, [Callum Akehurst-Ryan](https://www.linkedin.com/in/cakehurstryan/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) advises to [Start with the risks, not the method](https://cakehurstryan.com/2026/07/27/start-with-the-risks/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322).[thequalityduck.co.uk](https://www.thequalityduck.co.uk/understand-exploratory-testing-and-unlock-its-true-value/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) | | | | Automation | | [QA Is the Control Layer for AI-Assisted Development](https://juliapottinger.com/qa-control-layer-for-ai-assisted-development/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322)When AI can generate code and tests at speed, someone still has to check whether it makes sense. [Julia Pottinger](https://www.linkedin.com/in/julia-pottinger/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) walks through the five questions to ask before approving any AI-assisted change.Moreover, [Anil Singha](https://www.linkedin.com/in/anil-loutombam/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) wrote a high-level overview of [How I Built a Scalable Release Confidence Platform with Playwright, CI/CD, and AI](https://anilloutombam.medium.com/beyond-test-automation-be7b01d097ec?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322).[juliapottinger.com](https://juliapottinger.com/qa-control-layer-for-ai-assisted-development/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) | | [Self-Healing Tests with AI: Triage Before Repair](https://www.awesome-testing.com/2026/07/self-healing-tests-with-ai?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322)Looking for a solution for flaky tests? [Sławomir Radzymiński](https://www.linkedin.com/in/slawekradzyminski/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) walks through a practical example where an AI agent investigates the failure first and only opens a pull request when the evidence points to a test defect.Also, [Gleb Bahmutov](https://www.linkedin.com/in/bahmutov/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) explains why [End-to-end tests need to decide what can be retried to avoid flake](https://glebbahmutov.com/blog/what-needs-to-retry/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) with examples.[awesome-testing.com](https://www.awesome-testing.com/2026/07/self-healing-tests-with-ai?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) | | [Should Page Objects Assert? Where Test Assertions Belong](https://www.anton.qa/blog/posts/where-test-assertions-belong?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322)If you're not sure where to put assertions in your Playwright tests, [Anton Gulin](https://www.linkedin.com/in/antongulin/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) has a simple rule: page objects own the waiting, tests own the verdict, followed by advice on [Reusing One Page Object Method for Success and Failure Cases](https://www.anton.qa/blog/posts/reuse-page-object-method-success-and-failure?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322).[anton.qa](https://www.anton.qa/blog/posts/where-test-assertions-belong?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) | | [Visual Regression Testing: The Most Important Test You're Not Running](https://howtotestfrontend.com/resources/visual-regression-testing-introduction-guide?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322)This is a solid intro to visual regression testing, describing what it catches, how to fit it into your CI/CD pipeline and how to avoid flaky screenshot tests.Similarly, [Irfan Mujagić](https://www.linkedin.com/in/irfan-mujagi%C4%87-618435206/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) shows an example of why [Visual Diffing is a Change Detector. You Need a Correctness Detector.](https://www.thegreenreport.blog/articles/visual-diffing-is-a-change-detector-you-need-a-correctness-detector/visual-diffing-is-a-change-detector-you-need-a-correctness-detector.html?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322)[howtotestfrontend.com](https://howtotestfrontend.com/resources/visual-regression-testing-introduction-guide?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) | | [We Keep Patching Test Automation. Should We Rebuild & Reinvent It Instead?](https://chathuranga.space/notes/we-keep-patching-test-automation-should-we-rebuild-reinvent-it-instead?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322)An interesting read from [S Chathuranga Jayasinghe](https://www.linkedin.com/in/schathurangaj/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) who argues that UI tests break not because selectors move but because tests go through a scripted path instead of verifying a goal.[chathuranga.space](https://chathuranga.space/notes/we-keep-patching-test-automation-should-we-rebuild-reinvent-it-instead?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) | | | | Tools | | [A Practical Guide to Killing Playwright Flakiness for Good](https://medium.com/@ARaffaeSQA/why-your-playwright-tests-are-lying-to-you-a-practical-guide-to-killing-flakiness-for-good-2aeb5a92f552?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322)Good practical guide from [Abdur Raffae Masood](https://www.linkedin.com/in/abd-ur-raffae/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) on diagnosing flaky [Playwright](https://playwright.dev/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) tests, from DOM race conditions and CSS animations to parallel run resource issues, with code examples for each fix.Also, Katsuya Oura explains [Why using getByRole is better for AI agents](https://medium.com/@katsuya.ds/ai-agents-read-the-accessibility-tree-not-screenshots-why-getbyrole-doesnt-break-90a4c35c7eab?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322).[medium.com](https://medium.com/@ARaffaeSQA/why-your-playwright-tests-are-lying-to-you-a-practical-guide-to-killing-flakiness-for-good-2aeb5a92f552?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) | | [CLIs are more token-efficient than MCP. Or are they?](https://www.checklyhq.com/blog/mcp-vs-cli-token-efficiency/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322)This is interesting. [Stefan Judis](https://www.linkedin.com/in/stefan-judis/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) ran an experiment comparing MCP and CLI token usage for [Playwright](https://playwright.dev/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) agents and found no meaningful difference today — quite a change in just a few months!Speaking of that, [Julia Pottinger](https://www.linkedin.com/in/julia-pottinger/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) lists [MCPs Every QA Should Switch On](https://juliapottinger.com/mcps-every-qa-should-switch-on/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322), while [Andrii Cheparskyi](https://www.linkedin.com/in/cheparsky/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) shares [What Google's AI Tools Are Actually Worth to QA Right Now](https://medium.com/@cheparsky/ai-in-testing-13-what-googles-ai-tools-are-actually-worth-to-qa-right-now-2ee0a1b248ed?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322).[checklyhq.com](https://www.checklyhq.com/blog/mcp-vs-cli-token-efficiency/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) | | [How to Create Custom Fixtures in Playwright TypeScript](https://medium.com/@iamfaisalkhatri/4fa8b2fc2c82?sk=dc65288058ee17332bbffe9c08c8dcb2&utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322)If your Playwright test suite is growing and setup code keeps repeating everywhere, [Mohammad Faisal Khatri](https://www.linkedin.com/in/faisalkhatri/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) has a good practical guide on building custom fixtures to fix that. You can also learn [How to use Authentication setup in Playwright TypeScript](https://medium.com/@iamfaisalkhatri/f54bc68356f4?sk=9570464c5b3df5af8183e3c9adae5102&utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322).[medium.com](https://medium.com/@iamfaisalkhatri/4fa8b2fc2c82?sk=dc65288058ee17332bbffe9c08c8dcb2&utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) | | [Playwright 1.62: The Isolated Retries Release](https://testdino.com/blog/playwright-1-62-release?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322)[Playwright 1.62](https://playwright.dev/docs/release-notes?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322#version-162) brings isolated retries that separate resource problems from bugs. [Pratik Patel](https://www.linkedin.com/in/prat3ik/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) walks through every new feature with examples.Moreover, I also enjoyed [Svetlana Tretjakova](https://www.linkedin.com/in/svetlana-tretjakova-93147b136/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322)'s take on [Playwright: Why TypeScript and Not JavaScript?](https://medium.com/@svetlana.tretjakova/playwright-why-typescript-and-not-javascript-2b5fa4e78334?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) and [Combining UI and API in Playwright tests](https://medium.com/@svetlana.tretjakova/playwright-ui-and-api-tests-combined-772f660e734d?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322).[testdino.com](https://testdino.com/blog/playwright-1-62-release?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) | | [The first useful AI tool for QA may not be an autonomous tester](https://www.linkedin.com/pulse/first-useful-ai-tool-qa-may-autonomous-tester-sergei-krapivin-ivfdc/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322)Is your QA team sitting on years of test cases that no one can find? [Sergei Krapivin](https://www.linkedin.com/in/sergei-krapivin-aqa/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) makes a case for a small MCP server that does hybrid search over your existing test base and drafts new checklists with project context.[linkedin.com](https://www.linkedin.com/pulse/first-useful-ai-tool-qa-may-autonomous-tester-sergei-krapivin-ivfdc/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) | | | | Books | | [On QA, Muddy Water, Buddhism, and AI](https://qualitybits.tech/writing/on-muddied-water-buddhism-and-ai?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322)Inspired by the ["Mindfulness in Plain English"](https://www.goodreads.com/en/book/show/64369.Mindfulness%5Fin%5FPlain%5FEnglish?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) book, [Lina Zubyte](https://www.linkedin.com/in/linazubyte/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) shares a refreshing QA perspective on AI overload and the importance of pausing and questioning what really matters.[qualitybits.tech](https://qualitybits.tech/writing/on-muddied-water-buddhism-and-ai?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) | | | | Videos | | [Build Maintainable Playwright Tests With AI: A Complete Follow-Along](https://www.youtube.com/watch?v=wXu-6s92ZBo&utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322)In just 11 minutes, [Alex Khvastovich](https://www.linkedin.com/in/alexkhvastovich/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) showcases using AI to write Playwright tests, including resilient locators, page objects and official Playwright test agents.[youtube.com](https://www.youtube.com/watch?v=wXu-6s92ZBo&utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) | | [Test Automation Won't Save Your QA Career, but These Skills Will](https://www.youtube.com/watch?v=cnfNZ%5FlQzms&utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322)Yet another interesting talk. This time, [Joe Colantonio](https://www.linkedin.com/in/joecolantonio/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) invited [Keith Klain](https://www.linkedin.com/in/keithklain/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) for a 48-minute discussion on the future of the software tester's role.[youtube.com](https://www.youtube.com/watch?v=cnfNZ%5FlQzms&utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) | | | | And… | | [Born a Tester...](https://lnkd.in/p/ehHvVfsw?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-322) 😂 | | | | Thanks for reading!If you enjoy this newsletter and find it helpful in becoming a better tester, please consider sharing it with others.*[Dawid Dylowicz](https://www.linkedin.com/in/dawid-dylowicz/?ref=softwaretestingweekly.com)* |