@activate-core/test-forge 0.5.0 → 0.5.1

package/dist/core/ai-generator.js

@@ -12,7 +12,7 @@
  */
 import { execFileSync, spawn } from 'node:child_process';
 import { readFileSync, existsSync } from 'node:fs';
-import { loadConfig, splitCommand, withReadOnlyTools } from './config.js';
+import { loadConfig, splitCommand, withReadOnlyTools, resolveFramework, } from './config.js';
 const MAP_PATH = 'testforge.md';
 /**
  * Spawn a command, feed `input` on stdin, resolve with its stdout.
@@ -42,14 +42,10 @@ function runWithStdin(program, args, input) {
 export function buildPrompt(journey, map, testPath, focus) {
     const config = loadConfig();
     // Opinionated: testforge only generates Jest (api/backend) or Playwright
-    // (web/UI) tests. We look the framework up by AREA, but clamp anything
-    // that is not jest/supertest/playwright (e.g. a project's cypress setup)
-    // to the sensible default for the journey's Type — so no other framework
-    // ever leaks into generated output.
-    const configured = (config.framework?.[journey.area] ?? '').toLowerCase();
-    const isApi = configured === 'jest' ||
-        configured === 'supertest' ||
-        (configured !== 'playwright' && journey.type === 'api');
+    // (web/UI) tests — any other framework (e.g. a project's Cypress setup)
+    // is clamped to the right one for the journey. Single source of truth in
+    // resolveFramework, shared with the output-layout decision.
+    const isApi = resolveFramework(config, journey.area, journey.type) === 'jest';
     const framework = isApi
         ? 'Jest (with supertest for HTTP) for an API/backend test'
         : 'Playwright for a web/UI test';

package/dist/core/config.js

@@ -99,6 +99,19 @@ export function splitCommand(command) {
     const args = tokens.slice(1);
     return { program, args };
 }
+/**
+ * Resolve the test framework for a journey — clamped to the only two
+ * testforge supports. A web/UI journey is always Playwright (even if the
+ * project uses Cypress); an endpoint journey is Jest. This single source
+ * of truth drives BOTH the generation prompt and the output layout.
+ */
+export function resolveFramework(config, area, type) {
+    const configured = (config.framework?.[area] ?? '').toLowerCase();
+    const isApi = configured === 'jest' ||
+        configured === 'supertest' ||
+        (configured !== 'playwright' && type === 'api');
+    return isApi ? 'jest' : 'playwright';
+}
 /** Is this command Claude's CLI (so Claude-specific flags apply)? */
 function isClaude(program) {
     const base = program.split(/[\\/]/).pop() ?? program;

package/dist/core/run-generate.js

@@ -27,7 +27,7 @@ import { planSuite } from './suite-planner.js';
 import { isSyntaxValid } from './validate.js';
 import { hashContent, loadCache, saveCache } from './cache.js';
 import { findMarkdownFiles } from './find-files.js';
-import { loadConfig, testDirForType } from './config.js';
+import { loadConfig, testDirForType, resolveFramework } from './config.js';
 const CACHE_PATH = '.testforge/cache.json';
 /** How many times to re-ask the AI when output won't parse. */
 const MAX_GEN_ATTEMPTS = 2;
@@ -172,9 +172,17 @@ export async function runGenerate(docsDir, useAI = true, force = false, only) {
         // --journey <x>: generate just the one matching journey.
         if (only && !matchesJourney(file, journey.id, only))
             continue;
-        // Deep mode: each journey becomes a FOLDER of focused test files.
+        // Layout depends on the framework's test runner:
+        //  - Playwright (web/ops) recurses, so each journey gets its own
+        //    FOLDER of focused specs (testDir/<journey>/<slug>).
+        //  - Jest is often pointed at a flat glob (e.g. the-seam's
+        //    `**/service/*.test.js`, which does NOT recurse), so api/lambda
+        //    files stay FLAT in the test dir, journey-prefixed to stay unique
+        //    (testDir/<journey>-<slug>). Otherwise they'd silently not run.
         const areaDir = testDirForType(config, journey.area);
-        const testDir = join(areaDir, journey.id);
+        const framework = resolveFramework(config, journey.area, journey.type);
+        const flat = framework === 'jest';
+        const testDir = flat ? areaDir : join(areaDir, journey.id);
         const seedPath = join(seedDir, `${journey.id}${seedExt}`);
         // Skip if unchanged.
         if (!force && cache[file] === hash) {
@@ -201,7 +209,11 @@ export async function runGenerate(docsDir, useAI = true, force = false, only) {
         // call is independent, so a 15-file journey finishes in ~4 waves
         // instead of 15 serial calls.
         const generated = await pool(planned, GEN_CONCURRENCY, async (pf) => {
-            const filePath = join(testDir, `${pf.slug}${ext}`);
+            // Flat (jest): prefix the file with the journey so many journeys can
+            // share one dir without clashing. Folder (playwright): the journey
+            // folder already namespaces it, so the slug alone is enough.
+            const base = flat ? `${journey.id}-${pf.slug}` : pf.slug;
+            const filePath = join(testDir, `${base}${ext}`);
             let content;
             let status;
             if (useAI) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@activate-core/test-forge",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "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": {