QA Weekly Meeting 11th March
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3578564. -->
Reported by: [maddyt](https://www.drupal.org/user/3843187)
>>>
<h3>AI Initiative Weekly Catch-up – Summary</h3>
<h4>Drupal Pod Update (Tawny)</h4>
<ul>
<li>Core and CMS versions are now auto-detected and install the latest compatible versions, removing version issues for QA.</li>
<li>CI tests have been added to bash scripts, along with additional pipeline quality checks.</li>
<li>A new status report feature shows exactly which versions/modules were installed, making debugging much easier.</li>
<li>Extra modules can now be added easily for broader ecosystem testing (e.g. testing multiple AI modules together).</li>
<li>The project is considered stable and usable for a 1.0.x release.</li>
<li>Next step: align with Drupal Forge (Sal/Darren) before wider rollout.</li>
</ul>
<h4>Testing & QA</h4>
<ul>
<li>QA is ready to test once new tickets are created.</li>
<li>Release 1.3 was tested last week.</li>
<li>Clear markdown test instructions (like Marcus provided previously) are very helpful for QA.</li>
<li>A short demo walkthrough before testing would also help clarify the “happy path”.</li>
<li>Strong test documentation improves quality and often uncovers bugs during writing.</li>
</ul>
<h4>Promotion & Community Adoption</h4>
<ul>
<li>Plan to demo the tool in an upcoming sprint review.</li>
<li>Opportunity to promote more widely once v1 is confirmed.</li>
<li>Potential blog/documentation on Drupal.org about QA best practices and using “Needs QA” properly.</li>
<li>Arian offered to help promote via sprint slides and onboarding materials.</li>
</ul>
<h4>Open Points</h4>
<ul>
<li>Some edge cases remain (e.g. Context Control Center compatibility issues).</li>
<li>Would benefit from more testers, especially newer Drupal contributors.</li>
<li>Longer term: encourage broader contribution and possibly DevOps involvement.</li>
</ul>
issue