DrupalPod AI - Testing

🧪 QA scenarios — DrupalPod AI QA

The purpose of this ticket is to validate the DrupalPod AI QA tool — the browser extension, the DDEV config generator, and the DrupalForge launch flow.

The goal is to confirm that the tool correctly reads an issue, pre-populates the right environment variables, and delivers a working Drupal environment for testing.

For each scenario below, use the DrupalPod AI QA browser extension as your starting point.

The extension is Chrome-only for now. Install the extension, navigate to an AI module issue on drupal.org, and click the icon to begin.

Scenario 1 — Extension reads and pre-populates the issue correctly

1. Open an issue in the AI module queue on drupal.org.
2. Click the DrupalPod AI QA extension icon.
3. Confirm the extension panel displays the correct project type, module name, version, fork, and issue branch.
4. Record any fields that are missing, incorrect, or unexpectedly blank.

Pass: All fields correctly pre-populated. Fail: Any field is missing, wrong, or the extension does not open.

Scenario 2 — DDEV config generation

1. From the extension panel, click DDEV then Generate ddev config.
2. Confirm a .ddev/config.drupal.yaml is produced with correct values — check at minimum: DP_AI_MODULE, DP_AI_ISSUE_FORK, DP_AI_ISSUE_BRANCH, and DP_STARTER_TEMPLATE.
3. Drop the config into a DDEV project and run ddev restart.
4. Confirm the environment builds and the expected module version and branch are present.

Test with both AI 1.x and AI 2.x where possible.

Pass: Config correct, environment builds, correct branch checked out. Fail: Config missing values, build fails, or wrong branch.

Scenario 3 — DrupalForge launch

1. Log into DevPanel before starting.
2. From the extension panel, click DrupalForge then Launch DrupalForge.
3. Confirm you are redirected with environment variables pre-set.
4. Spin up the environment in DevPanel and confirm the correct module version and branch are present.

Test with both AI 1.x and AI 2.x where possible.

Pass: Redirect lands correctly, environment builds, correct branch active. Fail: Redirect missing variables, build fails, or wrong branch.

Scenario 4 — Version coverage

Where your setup allows, confirm the tooling works across these combinations. Test what you can and call out anything skipped.

• Drupal CMS 1 · AI 1.x · PHP 8.3 · DrupalForge
• Drupal CMS 1 · AI 1.x · PHP 8.3 · DDEV
• Drupal CMS 2 · AI 2.x · PHP 8.3 · DrupalForge
• Drupal CMS 2 · AI 2.x · PHP 8.3 · DDEV
• Drupal core 11.x · AI 2.x · PHP 8.3 · DrupalForge

Scenario 5 — Contrib module: AI Image Alt Text

Repeat the above testing using an issue from the AI Image Alt Text contrib module queue rather than the AI base module. This confirms the tooling works correctly when DP_TEST_MODULE is set to a contrib module.

1. Browse the AI Image Alt Text issue queue and select a suitable open issue — prioritise issues that have a patch or fork attached and clear reproduction steps.
2. Open the issue and click the DrupalPod AI QA extension icon.
3. Confirm the extension correctly identifies this as a contrib module issue and populates DP_TEST_MODULE, DP_TEST_MODULE_VERSION, DP_TEST_MODULE_ISSUE_FORK, and DP_TEST_MODULE_ISSUE_BRANCH in addition to the AI base fields.
4. Launch the environment via DDEV or DrupalForge (or both).
5. Confirm both the AI base module and the AI Image Alt Text module are installed and at the expected versions.
6. Where a fork is present, confirm the fork branch is checked out for the contrib module.
7. Vary your combinations across AI 1.x and AI 2.x — note whether behaviour or compatibility differs between versions.
8. Record the issue you selected, the combination tested, and the result.

Pass: Extension correctly identifies the contrib context, both modules present at correct versions, fork branch checked out where applicable. Fail: Contrib module fields missing or wrong, modules not installed, or wrong branch.

Versioning helper

When recording versions in your results, or if you need to override a version in the extension, use the following format:

• 1 = latest supported 1.x release line
• 1.2 = latest supported 1.2.x release line
• 1.x = the 1.x development branch
• 1.2.x = the 1.2.x development branch
• 1.2.3 = an exact tagged release
• Empty = auto-detect, or allow any version when the workflow supports it
• If testing a fork or issue branch, always provide the fork, the branch, and the matching module version
• Common examples for this work: Drupal CMS 1.x, Drupal CMS 2.x, AI 1.2.x, AI 2.0.x, PHP 8.2, PHP 8.3

Thank you! 🙏 Any issues with the extension or environment setup are exactly what we want to hear about here.