> ## 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 #328 - URL: https://softwaretestingweekly.com/issues/328/ - Published: 2026-09-25T07:30:23.000Z - Updated: 2026-09-25T07:30:23.000Z - Description: Artemis β€” Google's AI Agent for Android Testing πŸ“± - Author: Dawid Dylowicz | ![Dawid Dylowicz](https://storage.ghost.io/c/0c/e4/0ce4792b-e2e5-4f1a-9f93-b88f3b823672/content/images/2026/04/profile.png) Comment | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Welcome to the **328th** issue!There's something I've been waiting for.Google has open-sourced [Artemis](https://github.com/google/artemis?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) β€” an AI agent that tests Android apps on real phones and emulators.However, [Nicolas Dehandschoewercker](https://www.linkedin.com/in/nicolasdhnr/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) claims that Artemis reused code from their open-source [mobile-use](https://github.com/minitap-ai/mobile-use?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) project without credit β€” [I expected better from Google](https://www.minitap.ai/blog/i-expected-better-from-google?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328).Luckily, a day after that post, Google added the missing attribution.Happy testing!*[Dawid Dylowicz](https://www.linkedin.com/in/dawid-dylowicz/?ref=softwaretestingweekly.com)* | | | | Sponsored [Are you ready to work every weekend?](https://automatepro.com/blog/hot-fixes-service-now-weekly/?utm%5Fsource=paid+media&utm%5Fmedium=sponsorship&utm%5Fcampaign=software+testing+weekly+email)**ServiceNow Hot Fixes are now weekly!**Required to regression test every ServiceNow patch before production? That could mean 52 test cycles a year.[Here's everything ServiceNow testing teams need to know.](https://automatepro.com/blog/hot-fixes-service-now-weekly/?utm%5Fsource=paid+media&utm%5Fmedium=sponsorship&utm%5Fcampaign=software+testing+weekly+email)[automatepro.com](https://automatepro.com/blog/hot-fixes-service-now-weekly/?utm%5Fsource=paid+media&utm%5Fmedium=sponsorship&utm%5Fcampaign=software+testing+weekly+email) | | [Reach **9,285** software testers with a sponsored link β†’](https://softwaretestingweekly.com/sponsorship) | | | | News | | [18 Years in Quality Engineering: 10 Lessons I Wish I Had Learned Earlier](https://medium.com/@vishalgaikar%5F10062/18-years-in-quality-engineering-10-lessons-i-wish-i-had-learned-earlier-cc0efb8e8ab0?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328)It's always interesting to see how experienced testers look back at their career and share what they've learned. [Vishal Gaikar](https://www.linkedin.com/in/vishalgaikar/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) did just that after nearly two decades.Moreover, [Ramella Basenko](https://www.linkedin.com/in/ramella-basenko/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) adds one more lesson and explains why [The maturity of your QA process is capped by the maturity of your handoffs](https://medium.com/@ramellabasenko/the-maturity-of-your-qa-process-is-capped-by-the-maturity-of-your-handoffs-6a1de09e0e9c?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328).[medium.com](https://medium.com/@vishalgaikar%5F10062/18-years-in-quality-engineering-10-lessons-i-wish-i-had-learned-earlier-cc0efb8e8ab0?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) | | [AI Doesn't Test Your Product. It Tests Your PRD. Here's the Difference.](https://medium.com/@amrutalohabare/ai-doesnt-test-your-product-it-tests-your-prd-here-s-the-difference-c6f284ef2aef?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328)Wondering why your AI-generated tests don't find edge cases? [Amruta Lohabare](https://www.linkedin.com/in/amruta-lohabare-82017046/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) shares the prompt they now use to catch what it missed.Also, for a wider view, [Jason Arbon](https://www.linkedin.com/in/jasonarbon/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) compares [Testing: Human Experts vs. AI](https://jarbon.medium.com/testing-human-experts-vs-ai-a4a51fdbb361?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328).[medium.com](https://medium.com/@amrutalohabare/ai-doesnt-test-your-product-it-tests-your-prd-here-s-the-difference-c6f284ef2aef?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) | | [Hiring Is Asking for Fewer Skills and More Years. What That Means for Anyone Who Tests Code.](https://azevedorafaela.com/2026/09/09/hiring-is-asking-for-fewer-skills-and-more-years-what-that-means-for-anyone-who-tests-code/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328)[Rafaela Azevedo](https://www.linkedin.com/in/azevedorafaela/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) found an interesting trend β€” tech job openings now ask for more years of experience and list fewer skills. This signals that good judgment and experience matter more than pure tooling and coding excellence.At the same time, [Jaclyn Leigh](https://www.linkedin.com/in/jaclynlilly/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) looks beyond automation in [A Senior QE's Take on Modern Quality Engineering](https://insitepeek.net/blog/beyond-the-automation-checklist-a-senior-qes-take-on-modern-quality-engineering/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328).[azevedorafaela.com](https://azevedorafaela.com/2026/09/09/hiring-is-asking-for-fewer-skills-and-more-years-what-that-means-for-anyone-who-tests-code/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) | | [QA in Agile Development: Collaboration Without Bottlenecks](https://juliapottinger.com/qa-in-agile-development-without-bottlenecks/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328)Tired of testing everything at the end of a sprint? [Julia Pottinger](https://www.linkedin.com/in/julia-pottinger/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) shows how doing refinements and creating a shared Definition of Done can help you shift left.Similarly, [Matthew Sullivan](https://www.linkedin.com/in/matthew-sullivan-309b0722/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) asks what's left of agile in [The Agile Zombie](https://medium.com/@tldr%5Fhow%5Fto%5Ffix%5FQA/agile-is-dead-no-seriously-this-time-its-true-df400463eba6?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328), while [Khurram Bilal](https://www.linkedin.com/in/khurrambilal/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) suggests [Three Parallel Workstreams: Design, Build & Test on Day One](https://www.tech-sprinter.com/blog/the-three-parallel-workstreams-starting-design-build-and-test-on-day-one?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328).[juliapottinger.com](https://juliapottinger.com/qa-in-agile-development-without-bottlenecks/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) | | [Skilled manual QA are worth their weight in gold](https://www.reddit.com/r/QualityAssurance/comments/1wdqjqz/skilled%5Fmanual%5Fqa%5Fare%5Fworth%5Ftheir%5Fweight%5Fin%5Fgold/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328)Manual QA is dead? The contrary seems to be true. Someone on Reddit hired a junior tester whose thoroughness changed their mind and the community agrees.In a related thread, someone asks: [QA folks, how are you feeling about things these days?](https://www.reddit.com/r/QualityAssurance/comments/1wg6owh/qa%5Ffolks%5Fhow%5Fare%5Fyou%5Ffeeling%5Fabout%5Fthings%5Fthese/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328), to which [Betty Lin](https://www.linkedin.com/in/betty-lin-120b47a/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) responds [Why I Am Still Doing QA](https://medium.com/@betty.lin.twn/why-i-am-still-doing-qa-623d81dd1d75?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328).[reddit.com](https://www.reddit.com/r/QualityAssurance/comments/1wdqjqz/skilled%5Fmanual%5Fqa%5Fare%5Fworth%5Ftheir%5Fweight%5Fin%5Fgold/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) | | [Stop Gatekeeping, Start Underwriting: A New Operating Model for QA at AI Speed](https://medium.com/@imdevjyoti%5F49994/stop-gatekeeping-start-underwriting-a-new-operating-model-for-qa-at-ai-speed-fc179ea7f8dd?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328)We ship code faster, but we don't test faster. [Devjyoti Das](https://www.linkedin.com/in/devjyoti-das-b1136926/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) suggests that we should stop acting as a gate and price the risk of each change β€” just like insurance companies.Also, [Keith Klain](https://www.linkedin.com/in/keithklain/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) says that [Faster Agents Don't Remove the Bottleneck. They Move It](https://medium.com/@zyane/faster-agents-dont-remove-the-bottleneck-they-move-it-c996074ebe46?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328), which may lead to [Death by a Thousand Prompts](https://qualityremarks.com/death-by-a-thousand-prompts/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328), as [Zyane Tan](https://www.linkedin.com/in/zyane/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) points out.[medium.com](https://medium.com/@imdevjyoti%5F49994/stop-gatekeeping-start-underwriting-a-new-operating-model-for-qa-at-ai-speed-fc179ea7f8dd?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) | | | | Automation | | [AI Is Making Test Automation Faster. What About Maintainability?](https://www.linkedin.com/pulse/ai-making-test-automation-faster-what-maintainability-vaibhav-singhal-ygkff/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328)AI can help a tester write 30+ tests a day. But someone still has to understand and own that code. [Vaibhav Singhal](https://www.linkedin.com/in/vaibhav-singhal-29456b45/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) shares simple habits to keep it easy to maintain.Similarly, [Amruta Lohabare](https://www.linkedin.com/in/amruta-lohabare-82017046/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) advises us to [Stop Using AI Like a Fancy Autocomplete. Your Test Suite Deserves More.](https://medium.com/@amrutalohabare/stop-using-ai-like-a-fancy-autocomplete-your-test-suite-deserves-more-53bf84986728?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328)[linkedin.com](https://www.linkedin.com/pulse/ai-making-test-automation-faster-what-maintainability-vaibhav-singhal-ygkff/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) | | [Automation Coverage Is Not Test Coverage](https://ravirawal13.medium.com/automation-coverage-is-not-test-coverage-f5fb5f245fbf?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328)Does your dashboard report 90% automation? [Ravi Rawal](https://www.linkedin.com/in/ravi-rawal-13/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) shows why, even at that number, you can miss important failures, like a lost network connection or an expired token.On that note, [Balasundar Veluchamy](https://www.linkedin.com/in/balasundar-veluchamy-29486ab4/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) asks: [Your API Tests Pass. How Deeply?](https://aiqualityengineer.cc/your-api-tests-pass-how-deeply-8735c2cd2e00?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328)[ravirawal13.medium.com](https://ravirawal13.medium.com/automation-coverage-is-not-test-coverage-f5fb5f245fbf?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) | | [Computer Use Agents are Excellent QA Engineers](https://tristanrhodes.com/blog/Computer-Use-Agents-are-Excellent-QA-Engineers?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328)An interesting read from [Tristan Rhodes](https://www.linkedin.com/in/tristan-rhodes-a0a808228/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) outlining how to make computer-use AI agents work as a QA engineer. It tests each new feature overnight and reports bugs with screenshots and reproduction steps.Furthermore, if you plan to build your own, [Swati Seela](https://www.linkedin.com/in/swatiseela/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) shares: [Can an AI Agent Perform Exploratory Testing? 5 Lessons from Building One](https://aiqualityengineer.cc/can-an-ai-agent-perform-exploratory-testing-5-lessons-from-building-one-21b9b99cf36a?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328).[tristanrhodes.com](https://tristanrhodes.com/blog/Computer-Use-Agents-are-Excellent-QA-Engineers?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) | | [Stop Building Test Frameworks. Start Building Products.](https://medium.com/@muskanjini/stop-building-test-frameworks-start-building-products-e0c0e8426456?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328)Internal test frameworks may grow over time without much planning. [Muskan Agarwal](https://www.linkedin.com/in/muskanagarwal14/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) says it's risky and explains why we should treat it as a public library, with versions, a changelog and working examples.Also, Muskan says that [Every Bug Report Is a Test Case You Forgot to Write](https://medium.com/@muskanjini/every-bug-report-is-a-test-case-you-forgot-to-write-5187700fbed2?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328).[medium.com](https://medium.com/@muskanjini/stop-building-test-frameworks-start-building-products-e0c0e8426456?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) | | [The day my CI went red for a reason my code didn't cause](https://medium.com/@prathammhatre5/a-ci-regression-gate-caught-a-bug-i-didnt-write-19ab1796b2ac?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328)Running LLM evals in CI? [Pratham Mhatre](https://www.linkedin.com/in/prathammhatre/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) shares a story about how a single run may not always provide enough evidence, and how to properly interpret the results.What's more, [Jaren Charles Cudilla](https://www.linkedin.com/in/jarencharlescudilla/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) describes [Database QA: The Bugs Your UI Tests Will Never Catch](https://qajourney.net/database-qa-bugs-ui-tests-miss/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328).[medium.com](https://medium.com/@prathammhatre5/a-ci-regression-gate-caught-a-bug-i-didnt-write-19ab1796b2ac?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) | | | | Tools | | [Let's save the clues from a failed Playwright test](https://www.anton.qa/blog/posts/save-failed-playwright-test?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328)If you're struggling to debug a flaky [Playwright](https://playwright.dev/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) test, [Anton Gulin](https://www.linkedin.com/in/antongulin/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) advises keeping a trace of the failed attempt, not just the retry that passed.Also, [Richard Forjoe](https://www.linkedin.com/in/richardforjoe/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) shares another useful Playwright tip in [Playwright β€” Run Only the E2E Tests a Pull Request Can Actually Break](https://medium.com/@rforjoe/playwright-run-only-the-e2e-tests-a-pull-request-can-actually-break-676c01c9b6f2?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328).[anton.qa](https://www.anton.qa/blog/posts/save-failed-playwright-test?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) | | [Playwright 1.63: The Update Where Your Tests Finally Learn to Share](https://medium.com/@fida.brrjeb/playwright-1-63-the-update-where-your-tests-finally-learn-to-share-696be53901af?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328)[Playwright](https://playwright.dev/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) 1.63 is a significant release and [Fidaa Berrjeb](https://www.linkedin.com/in/fidaabrj/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) describes the new features with code examples: test locks, locator.visible() and clearer steps in the trace viewer that can make your test suite easier to run and debug.Similarly, [Svetlana Tretjakova](https://www.linkedin.com/in/svetlana-tretjakova-93147b136/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) gives another good overview in [Playwright 1.63 Is Here: The Updates QA Engineers Should Actually Care About](https://medium.com/@svetlana.tretjakova/playwright-1-63-is-here-the-updates-qa-engineers-should-actually-care-about-8d2f41490013?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328).[medium.com](https://medium.com/@fida.brrjeb/playwright-1-63-the-update-where-your-tests-finally-learn-to-share-696be53901af?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) | | [Playwright MCP Tutorial: How to Generate Tests with AI](https://medium.com/@michael-brown-/playwright-mcp-tutorial-how-to-generate-tests-with-ai-66b0403ecc26?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328)Thinking about AI-generated [Playwright](https://playwright.dev/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) tests? [Michael Brown](https://medium.com/@michael-brown-?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) compares Playwright MCP with codegen and explains when to use each one, including advice on security.Moreover, [Svetlana Tretjakova](https://www.linkedin.com/in/svetlana-tretjakova-93147b136/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) has good advice for any Playwright suite: [Stop Mocking Everything: Advanced Network Interception in Playwright](https://medium.com/@svetlana.tretjakova/stop-mocking-everything-advanced-network-interception-in-playwright-abfa48caf4d6?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328)[medium.com](https://medium.com/@michael-brown-/playwright-mcp-tutorial-how-to-generate-tests-with-ai-66b0403ecc26?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) | | [Testing Node.js + TypeScript APIs the Right Way (Vitest + Supertest)](https://medium.com/@chiragmehta900/testing-node-js-typescript-apis-the-right-way-vitest-supertest-615106284952?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328)If you write Node.js and TypeScript APIs, [Chirag Mehta](https://www.linkedin.com/in/chiragmehta900/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) has a hands-on guide to testing them with [Vitest](https://vitest.dev/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) and [Supertest](https://github.com/forwardemail/supertest?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328), including how to mock and gate CI on coverage.And if you use Java, here's a good question by [Andrii Olieinik](https://www.linkedin.com/in/andrii-olieinik/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328): [What Is a Test Fixture in JUnit, and Why Is @BeforeEach Not the Fixture?](https://medium.com/javarevisited/what-is-a-test-fixture-in-junit-and-why-is-beforeeach-not-the-fixture-53f5c750270e?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328#6139)[medium.com](https://medium.com/@chiragmehta900/testing-node-js-typescript-apis-the-right-way-vitest-supertest-615106284952?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) | | | | Books | | [Creative teamwork for quality – A Review of "Sidewinder – Creative Missile Development at China Lake"](https://testandanalysis.home.blog/2026/09/15/creative-teamwork-for-quality-a-review-of-sidewinder-creative-missile-development-at-china-lake-by-ron-westrum/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328)An unusual [book](https://www.goodreads.com/en/book/show/1332894.Sidewinder?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) review from [Mike Harris](https://www.linkedin.com/in/mike-harris-citp-fbcs/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) on what we can learn from the team behind the Sidewinder missile, like fast feedback from testing and close contact with the people who use the product.[testandanalysis.home.blog](https://testandanalysis.home.blog/2026/09/15/creative-teamwork-for-quality-a-review-of-sidewinder-creative-missile-development-at-china-lake-by-ron-westrum/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) | | | | Videos | | [How to Stay Irreplaceable When Agents Write Your Tests](https://www.youtube.com/watch?v=QZcHudkWHuM&utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328)Continuing the series of interviews, this time [Joe Colantonio](https://www.linkedin.com/in/joecolantonio/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) invited [Jonathon Wright](https://www.linkedin.com/in/automation/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) to discuss the impact of agents on testers' role and test automation in this 34-minute recording.[youtube.com](https://www.youtube.com/watch?v=QZcHudkWHuM&utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) | | [Playwright Lock: Stop Parallel Tests from Breaking](https://www.youtube.com/watch?v=y3aPNYd%5Fk00&utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328)I mentioned above the new features in Playwright 1.63, and here's a more detailed deep dive by [Joan Esquivel Montero](https://www.linkedin.com/in/joanesquivel/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) into Test Locks.In addition to that, [JΓ©rΓ©mie Fleurant](https://www.linkedin.com/in/jeremie-fleurant?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) explains what's [Beyond Playwright Test Locks: Pooling Shared Test Users](https://medium.com/@jeremie.fleurant/beyond-playwright-test-locks-pooling-shared-test-users-f5f2544f919f?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328).[youtube.com](https://www.youtube.com/watch?v=y3aPNYd%5Fk00&utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) | | | | And… | | [Must be an AI issue...](https://www.reddit.com/r/ProgrammerHumor/comments/1wix3c2/moderndevsvsmoderndevops/?utm%5Fsource=softwaretestingweekly&utm%5Fmedium=email&utm%5Fcampaign=issue-328) πŸ˜‚ | | | | 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)* |