>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3570117. --> Reported by: [maddyt](https://www.drupal.org/user/3843187) >>> <p><strong>Update Summary: </strong>[QA Meeting 28th January 2026]<br> <strong>Check-in Date: </strong>01/28/2026<br> <strong>Additional Collaborators: </strong> Zoocha<br> <em>Metadata is used by the <a href="https://www.drupalstarforge.ai/" title="AI Tracker">AI Tracker.</a> Docs and additional fields <a href="https://www.drupalstarforge.ai/ai-dashboard/docs" title="AI Issue Tracker Documentation">here</a>.</em></p> <p><strong>Summary</strong></p> <ul> <li>Tawny Bartlett gave a demo held of a new DrupalPod Chrome extension to simplify spinning up test environments directly from Drupal.org issues</li> <li>Extension reads issue data (project, fork, branch, versions) and generates configurations for: <ul> <li>DDEV (local testing)</li> <li>DrupalPod / Drupal Forge (cloud testing)</li> </ul> </li> <li>Initial focus is on AI initiative modules, but the approach is reusable for other contributed projects</li> </ul> <p> <br></p> <p><strong>Current Status</strong></p> <ul> <li>Chrome extension is available via an unlisted Chrome Web Store URL</li> <li>Core functionality is working but the project is still early-stage</li> <li>Known limitations identified: <ul> <li>Drupal Forge authentication can drop the launch request during sign-in</li> <li>Identical environments cannot be rebuilt within ~6 hours</li> <li>Cloud builds take ~6 minutes</li> <li>Some module enablement issues observed</li> </ul> </li> </ul> <p> <br></p> <p><strong>Next Steps</strong></p> <ul> <li>QA team to begin structured testing across multiple issues and version combinations</li> <li>Test CMS vs Core, AI 1.x vs 2.x, and DDEV vs Drupal Forge</li> <li>Log all bugs and UX issues directly in the Drupal.org issue queue</li> <li>Draft QA-friendly documentation based on testing experience</li> <li>Follow up with Drupal Forge maintainers on authentication and rebuild limitations</li> </ul> <p> <br></p>