>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3577022. --> Reported by: [maddyt](https://www.drupal.org/user/3843187) >>> <p> <strong>Update Summary: </strong> Weekly QA Meeting<br> <strong>Check-in Date: </strong>03/04/2026</p> <h3>AI Initiative Weekly Catch-up &ndash; Summary</h3> <h4>QA &amp; Release Update</h4> <ul> <li>The QA team is expecting the next release tomorrow and will begin testing once it&rsquo;s ready.</li> <li>This will be their first full release test, and they&rsquo;ll share a report with evidence afterwards.</li> <li>Marcus confirmed Release Candidate 2 is nearly ready. Six bugs were found during prep and are being fixed ahead of QA.</li> <li>A detailed testing script covering all new 1.3 features has been prepared.</li> </ul> <h4>AI Testing Experiments</h4> <ul> <li>Marcus has been experimenting with an AI-driven functional testing setup using Claude, Playwright, FFmpeg and 11 Labs.</li> <li>It can follow issue steps, test in a browser, and generate a narrated video of the process.</li> <li>The idea is to eventually auto-generate functional tests and run them on tagged releases rather than every merge.</li> <li>It&rsquo;s still experimental, but shows strong potential.</li> </ul> <h4>Wider Discussion</h4> <ul> <li>The AI initiative is pushing innovation quickly, potentially leading the way for wider Drupal improvements.</li> <li>Zoocha currently uses Cypress for testing, and there may be an opportunity to collaborate around Playwright expertise.</li> </ul> <h4>Next Steps</h4> <ul> <li>QA to test the upcoming release and share results.</li> <li>Catch up again next week for further Drupal Pod updates.</li> </ul>