@activate-core/test-forge 0.9.5 → 0.9.7

package/dist/core/ai-generator.js

@@ -121,9 +121,16 @@ export function buildPrompt(journey, map, testPath, focus, harnessPath) {
             ].join('\n')
             : [
                 `Because this is a web journey, write Playwright tests that drive`,
-                `the UI. Use placeholder selectors with a TODO comment where the`,
-                `real page structure is unknown — do not invent selectors as if`,
-                `they are real.`,
+                `the UI. FIRST find the REAL selectors: with your read-only tools,`,
+                `locate and READ this page's actual React/Vue components (grep the`,
+                `webapp source for the route, page name, and on-screen text, then`,
+                `open those component files). Use the selectors that genuinely`,
+                `exist there — data-testid/data-cy, input name/id, aria-role,`,
+                `label text, or button text — via Playwright locators`,
+                `(getByRole/getByLabel/getByTestId/getByText). Only leave a`,
+                `"// TODO: confirm selector" when the element truly cannot be`,
+                `found in the component source; do NOT default everything to a`,
+                `TODO. Never invent a selector as if it were real.`,
                 `CRITICAL Playwright API: import { test, expect } from`,
                 `'@playwright/test'. There is NO test.todo / it.* / describe.skip`,
                 `in Playwright — using them throws at collection and breaks the`,

package/dist/core/run-generate.js

@@ -215,6 +215,15 @@ export async function runGenerate(docsDir, useAI = true, force = false, only, ar
         if (harnessByArea.has(area))
             return harnessByArea.get(area) ?? undefined;
         const info = harnessInfo(areaDir, framework, ext);
+        // REUSE an existing testkit instead of regenerating it. This is what
+        // makes one-by-one (`generate --journey X`) cheap: the first journey
+        // in an area builds the testkit, every later journey reuses it — no
+        // extra AI call (and no risk of that call eating the token limit).
+        // Pass --force to rebuild a stale testkit (e.g. after upgrading).
+        if (!force && existsSync(info.path)) {
+            harnessByArea.set(area, info.path);
+            return info.path;
+        }
         const kit = await generateValidatedAsync(() => generateHarnessAsync(info.path, framework), ext.endsWith('.js') ? '.js' : '.ts');
         if (kit === null) {
             harnessByArea.set(area, null);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@activate-core/test-forge",
-  "version": "0.9.5",
+  "version": "0.9.7",
   "description": "AI-powered QA automation. Scans a project, drafts journey docs, and generates seeded Jest/Playwright tests. Works in any project, with any AI CLI.",
   "type": "module",
   "bin": {