QA Weekly Meeting - 1st April 2026
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3582760. -->
Reported by: [maddyt](https://www.drupal.org/user/3843187)
>>>
<p><strong>Update Summary: </strong> QA Weekly Meeting - 1st April 2026<br>
<strong>Check-in Date: </strong>04/01/2026</p>
<p><strong>Key Updates</strong></p>
<ul>
<li> <strong>Provider Selection Feature</strong><br> A new feature allows users to select an AI provider (e.g. OpenAI) during environment setup. A supporting module has been added to handle API key input and automatic environment expiry (4 hours). This is now merged and ready for testing. </li>
<li> <strong>Demo Progress</strong><br> Work is ongoing to produce a recorded demo. Local development (via DDEV) is working reliably, but demo creation has been slowed by tooling and recording challenges. </li>
<li> <strong>Drupal Forge Blocker</strong><br> A critical issue is preventing authentication within the Drupal Forge flow (likely related to token/SSO handling). This blocks full end-to-end demos.
<p> Additional issues include:
</p><ul>
<li>Failed authentication prevents reuse of environment variables for up to 6 hours.</li>
<li>Issue appears to be platform-level (not project-specific).</li>
</ul>
<p> This requires investigation with the Drupal Forge team. </p></li>
<li> <strong>Project Stability</strong><br> The project is in a stable state:
<ul>
<li>Tests are passing.</li>
<li>Recent version conflicts highlighted improvements in compatibility handling.</li>
</ul>
</li>
<li> <strong>Alternative Infrastructure (Tugboat)</strong><br> Tugboat was identified as a potential alternative for automatically creating test environments per PR.<br> This is not an immediate priority but may be explored as a future enhancement, given the project’s infrastructure-agnostic approach. </li>
<li> <strong>Documentation Approach</strong><br> Documentation should be prioritised over demo completion to unblock usage.<br> Recommended approach:
<ul>
<li>Publish documentation early to enable testing.</li>
<li>Host documentation using MKDocs within the project repository.</li>
</ul>
</li>
<li> <strong>QA Collaboration Opportunities</strong><br> There is an opportunity for the QA team to support:
<ul>
<li>Regular release testing (bi-weekly patch releases).</li>
<li>Feature testing where issues are marked as “Needs QA”.</li>
<li>Automation of repeatable QA scripts.</li>
</ul>
<p> Additional improvements include introducing stricter QA expectations before issues are marked RTBC. </p></li>
</ul>
<hr>
<p><strong>Next Steps</strong></p>
<ul>
<li>Contact Drupal Forge team to investigate authentication and environment reuse issues.</li>
<li>Share reproducible examples (video + details) with Drupal Forge for debugging.</li>
<li>Prioritise publishing documentation to enable early usage and feedback.</li>
<li>Continue work on recording a full demo (once blocking issues are resolved).</li>
<li>Test the new provider selection and environment expiry functionality.</li>
<li>Explore QA support for release testing and feature validation.</li>
<li>Capture Tugboat as a potential future enhancement.</li>
</ul>
<hr>
<p><strong>Overall Direction</strong></p>
<p>The project is functionally stable and close to being demo-ready. The primary blocker is Drupal Forge authentication, which must be resolved before full demonstration and broader promotion. In parallel, documentation and QA processes can progress to enable early community engagement.</p>
issue