@bugzy-ai/bugzy 1.12.1 → 1.12.2

package/dist/cli/index.cjs

@@ -1633,6 +1633,19 @@ Create or update test case files in \`./test-cases/\` for the new feature:
 - Include: objective, preconditions, test steps, expected results
 - Mark \`automated: true\` for scenarios that should be automated
 
+### Handle Missing Test Data
+
+If the Jira issue or PR references test accounts/data (e.g., TEST_PREMIUM_USER, TEST_ADMIN_PASSWORD) that don't exist in \`.env.testdata\`:
+
+1. **DO NOT skip test creation** \u2014 missing data is not a blocker for writing tests
+2. Add placeholder entries to \`.env.testdata\` for non-secret variables (empty value with comment)
+3. Reference all variables as \`process.env.VAR_NAME\` in test code \u2014 they'll resolve at runtime
+4. Create the test cases and specs normally \u2014 tests may fail until data is configured, which is expected
+5. {{INVOKE_TEAM_COMMUNICATOR}} to notify the team about missing test data that needs to be configured
+6. Include in the Slack message: which variables are missing, what values they need, and which tests depend on them
+
+**CRITICAL**: Never conclude "manual verification required" or "BLOCKED" solely because test data is missing. Always create the test artifacts first.
+
 ### Generate Playwright Specs
 
 {{INVOKE_TEST_CODE_GENERATOR}} to create automated test specs:
@@ -2756,6 +2769,7 @@ var CONTENT2 = `You are an expert Playwright test automation engineer specializi
    - Reference variables using \`process.env.VAR_NAME\` in tests
    - Add new required variables to \`.env.testdata\`
    - NEVER read \`.env\` file (secrets only)
+   - **If a required variable is missing from \`.env.testdata\`**: Add it with an empty value and a \`# TODO: configure\` comment. Continue creating tests using \`process.env.VAR_NAME\` \u2014 tests will fail until configured, which is expected. Do NOT skip test creation because of missing data.
 
 3. ${MEMORY_READ_INSTRUCTIONS.replace(/{ROLE}/g, "test-code-generator")}
 
@@ -7513,7 +7527,8 @@ Before adding ANY variable to .env.testdata, check if it's a secret:
 1. Scan for TEST_* variable references in test plan and test cases
 2. For each variable found:
    - If name contains PASSWORD/SECRET/TOKEN/KEY -> Skip (it's a secret, goes in .env only)
-   - Otherwise -> Add to .env.testdata with actual value
+   - If actual value is known -> Add to .env.testdata with value
+   - If actual value is unknown -> Add to .env.testdata with empty value and \`# TODO: team to configure\` comment
 3. Preserve existing variables in .env.testdata
 
 **Example .env.testdata (non-secrets only):**