test(featureDev): use env var to enable very slow test aws#7201

## Problem

The default 5-minute timeout was insufficient for Amazon Q Feature Dev
tests that involve code generation with multiple iterations. This was
causing tests to fail prematurely before they could complete their full
execution cycle.

## Solution

Extended the test timeout to 15 minutes (900,000ms) specifically for the
code generation test with multi-iteration scenarios. This provides
adequate time for multi-iteration code generation tests to complete
their execution while maintaining the existing test behavior.

Author: chengoramazon

CONTRIBUTING.md

@@ -534,6 +534,7 @@ Unlike the user setting overrides, not all of these environment variables have t
 -   `AWS_TOOLKIT_TEST_NO_COLOR`: If the tests should include colour in their output
 -   `DEVELOPMENT_PATH`: The path to the aws toolkit vscode project
 -   `TEST_DIR` - The directory where the test runner should find the tests
+-   `AMAZONQ_FEATUREDEV_ITERATION_TEST` - Controls whether to enable multiple iteration testing for Amazon Q feature development
 
 ### SAM/CFN ("goformation") JSON schema
 

packages/amazonq/test/e2e/amazonq/featureDev.test.ts

@@ -166,6 +166,12 @@ describe('Amazon Q Feature Dev', function () {
 
     describe('/dev {msg} entry', async () => {
         beforeEach(async function () {
+            const isMultiIterationTestsEnabled = process.env['AMAZONQ_FEATUREDEV_ITERATION_TEST'] // Controls whether to enable multiple iteration testing for Amazon Q feature development
+            if (!isMultiIterationTestsEnabled) {
+                this.skip()
+            } else {
+                this.timeout(900000) // Code Gen with multi-iterations requires longer than default timeout(5 mins).
+            }
             tab = framework.createTab()
             tab.addChatMessage({ command: '/dev', prompt })
             tab = framework.getSelectedTab()