@validate.qa/runner 1.0.20 → 1.0.21

package/dist/cli.js

@@ -66068,6 +66068,8 @@ ${constraints.join("\n")}`);
     function buildMobileFallbackScenarios(input) {
       if (input.mode === "survey")
         return [];
+      if (input.featureName?.trim())
+        return [];
       const orderedScreens = targetAppScreens(input.graph, input.appId).filter((state2) => state2.screenType?.toLowerCase() !== "error").filter((state2) => state2.visited || state2.firstSeenIteration === 0).sort((a, b) => a.firstSeenIteration - b.firstSeenIteration);
       if (orderedScreens.length === 0)
         return [];
@@ -66215,6 +66217,15 @@ ${constraints.join("\n")}`);
             fallbackReason: result.fallbackReason ?? "Mobile planner produced no scenarios"
           };
         }
+        if (input.featureName?.trim()) {
+          return {
+            ...result,
+            featureGroups: mobileFeatureGroups,
+            warning: [result.warning, `Deep discovery could not plan any scenarios for "${input.featureName}" \u2014 the explorer did not reach that feature's screens this run. If the feature requires a signed-in session, verify TEST_USER_EMAIL / TEST_USER_PASSWORD are valid for this app, then re-run.`].filter(Boolean).join(" | "),
+            fallbackUsed: true,
+            fallbackReason: result.fallbackReason ?? `Planner produced no scenarios for feature "${input.featureName}"`
+          };
+        }
       }
       if (input.mode === "survey" && result.featureGroups.length === 0 && mobileFeatureGroups.length > 0) {
         return {
@@ -66495,7 +66506,8 @@ Max iterations: ${MAX_SCENARIO_ITERATIONS}. You will be warned near the end.`;
 This app has stored login credentials under these keys:
 ${keyList}
 
-When a scenario needs a signed-in session or fills a login/sign-up form, fill each credential field with \`mobile_fill_credential\`: pass the field ref and the KEY (e.g. \`{ ref: "e5", credentialKey: "TEST_USER_EMAIL" }\`). The runner types the real value on the device and the generated test stores a \`{{KEY}}\` placeholder that replay resolves \u2014 you never see, log, or echo the secret.
+When a scenario needs a signed-in session, complete the FULL login sequence \u2014 filling the fields alone does NOT log you in:
+1. Reach the email/password form. 2. Fill each credential field with \`mobile_fill_credential\` (pass the field ref and the KEY, e.g. \`{ ref: "e5", credentialKey: "TEST_USER_EMAIL" }\`) \u2014 the runner types the real value on the device and the generated test stores a \`{{KEY}}\` placeholder that replay resolves; you never see the secret. 3. TAP THE SUBMIT button (Sign In / Log In / Continue). 4. Re-snapshot and VERIFY an authenticated screen appeared. If login fails twice, do NOT keep retrying or wander: call finish_generate with verified:false and say the login could not be completed (the credentials may be invalid for this app).
 
 SECURITY RULES:
 - NEVER call \`mobile_type\` with a real email, password, or token value \u2014 the runner will REJECT the call and you lose an iteration. Use \`mobile_fill_credential\` for every credential field.
@@ -328471,7 +328483,7 @@ var require_package4 = __commonJS({
   "package.json"(exports2, module2) {
     module2.exports = {
       name: "@validate.qa/runner",
-      version: "1.0.20",
+      version: "1.0.21",
       description: "validate local test runner - execute Playwright tests on your machine, connected to validate.qa cloud.",
       bin: {
         "validate-runner": "dist/cli.js"

package/dist/cli.mjs

@@ -66073,6 +66073,8 @@ ${constraints.join("\n")}`);
     function buildMobileFallbackScenarios(input) {
       if (input.mode === "survey")
         return [];
+      if (input.featureName?.trim())
+        return [];
       const orderedScreens = targetAppScreens(input.graph, input.appId).filter((state2) => state2.screenType?.toLowerCase() !== "error").filter((state2) => state2.visited || state2.firstSeenIteration === 0).sort((a, b) => a.firstSeenIteration - b.firstSeenIteration);
       if (orderedScreens.length === 0)
         return [];
@@ -66220,6 +66222,15 @@ ${constraints.join("\n")}`);
             fallbackReason: result.fallbackReason ?? "Mobile planner produced no scenarios"
           };
         }
+        if (input.featureName?.trim()) {
+          return {
+            ...result,
+            featureGroups: mobileFeatureGroups,
+            warning: [result.warning, `Deep discovery could not plan any scenarios for "${input.featureName}" \u2014 the explorer did not reach that feature's screens this run. If the feature requires a signed-in session, verify TEST_USER_EMAIL / TEST_USER_PASSWORD are valid for this app, then re-run.`].filter(Boolean).join(" | "),
+            fallbackUsed: true,
+            fallbackReason: result.fallbackReason ?? `Planner produced no scenarios for feature "${input.featureName}"`
+          };
+        }
       }
       if (input.mode === "survey" && result.featureGroups.length === 0 && mobileFeatureGroups.length > 0) {
         return {
@@ -66500,7 +66511,8 @@ Max iterations: ${MAX_SCENARIO_ITERATIONS}. You will be warned near the end.`;
 This app has stored login credentials under these keys:
 ${keyList}
 
-When a scenario needs a signed-in session or fills a login/sign-up form, fill each credential field with \`mobile_fill_credential\`: pass the field ref and the KEY (e.g. \`{ ref: "e5", credentialKey: "TEST_USER_EMAIL" }\`). The runner types the real value on the device and the generated test stores a \`{{KEY}}\` placeholder that replay resolves \u2014 you never see, log, or echo the secret.
+When a scenario needs a signed-in session, complete the FULL login sequence \u2014 filling the fields alone does NOT log you in:
+1. Reach the email/password form. 2. Fill each credential field with \`mobile_fill_credential\` (pass the field ref and the KEY, e.g. \`{ ref: "e5", credentialKey: "TEST_USER_EMAIL" }\`) \u2014 the runner types the real value on the device and the generated test stores a \`{{KEY}}\` placeholder that replay resolves; you never see the secret. 3. TAP THE SUBMIT button (Sign In / Log In / Continue). 4. Re-snapshot and VERIFY an authenticated screen appeared. If login fails twice, do NOT keep retrying or wander: call finish_generate with verified:false and say the login could not be completed (the credentials may be invalid for this app).
 
 SECURITY RULES:
 - NEVER call \`mobile_type\` with a real email, password, or token value \u2014 the runner will REJECT the call and you lose an iteration. Use \`mobile_fill_credential\` for every credential field.
@@ -328476,7 +328488,7 @@ var require_package4 = __commonJS({
   "package.json"(exports, module) {
     module.exports = {
       name: "@validate.qa/runner",
-      version: "1.0.20",
+      version: "1.0.21",
       description: "validate local test runner - execute Playwright tests on your machine, connected to validate.qa cloud.",
       bin: {
         "validate-runner": "dist/cli.js"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@validate.qa/runner",
-  "version": "1.0.20",
+  "version": "1.0.21",
   "description": "validate local test runner - execute Playwright tests on your machine, connected to validate.qa cloud.",
   "bin": {
     "validate-runner": "dist/cli.js"