test(qa): keep image generation fixture on mock lane

vincentkoc · vincentkoc · commit 43f2b61f3b01 · 2026-06-23T02:35:02.000+02:00
diff --git a/extensions/qa-lab/src/scenario-catalog.test.ts b/extensions/qa-lab/src/scenario-catalog.test.ts
@@ -248,6 +248,7 @@ describe("qa scenario catalog", () => {
     });
     expect(readQaScenarioExecutionConfig(webSearch.id)).not.toHaveProperty("knownHarnessGap");
     expect(readQaScenarioExecutionConfig(imageGenerate.id)).toMatchObject({
+      requiredProviderMode: "mock-openai",
       toolName: "image_generate",
       toolCoverage: {
         bucket: "openclaw-dynamic-integration",
diff --git a/qa/scenarios/runtime/tools/image-generate.yaml b/qa/scenarios/runtime/tools/image-generate.yaml
@@ -9,6 +9,7 @@ scenario:
       - tools.image-generate
   objective: Verify image_generate preserves arguments and result shape across OpenClaw and Codex.
   successCriteria:
+    - Scenario is mock-openai only because live image generation uses async task lifecycle proof outside this direct failure-path fixture.
     - Effective tools expose image_generate after QA image-generation config is applied.
     - The mock provider plans exactly one happy-path image_generate call.
     - The mock provider plans one denied-input failure-path image_generate call.
@@ -22,6 +23,7 @@ scenario:
     kind: flow
     summary: Exercise the image_generate runtime tool family.
     config:
+      requiredProviderMode: mock-openai
       toolName: image_generate
       ensureImageGeneration: true
       toolCoverage:
@@ -42,6 +44,9 @@ flow:
   steps:
     - name: exercises image_generate happy and failure paths
       actions:
+        - assert:
+            expr: "env.providerMode === config.requiredProviderMode"
+            message: this seeded scenario is mock-openai only
         - call: runRuntimeToolFixture
           saveAs: result
           args:
