@activate-core/test-forge 0.3.0 → 0.4.0

package/dist/core/ai-generator.js

@@ -17,13 +17,18 @@ const MAP_PATH = 'testforge.md';
 /** Build the prompt we send to the AI for one journey. */
 export function buildPrompt(journey, map, testPath) {
     const config = loadConfig();
-    const fw = config.framework?.[journey.type];
-    const isApi = journey.type === 'api' || fw === 'jest' || fw === 'supertest';
-    const framework = fw
-        ? `${fw} for a "${journey.type}" test`
-        : isApi
-            ? 'Jest (with supertest for HTTP) for an API/backend test'
-            : 'an appropriate test framework for this kind of journey';
+    // 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');
+    const framework = isApi
+        ? 'Jest (with supertest for HTTP) for an API/backend test'
+        : 'Playwright for a web/UI test';
     const ext = config.testExtension ?? '.test.ts';
     const isJs = ext.endsWith('.js');
     const language = isJs

package/dist/core/config.js

@@ -127,6 +127,35 @@ export function withEditTools(cmd) {
         args: [...cmd.args, '--permission-mode', 'acceptEdits'],
     };
 }
+/**
+ * Tools an external reference may need to be read: fetching a web page or
+ * a Notion doc. `acceptEdits` only auto-approves file edits, so a headless
+ * `claude -p` would otherwise be DENIED web/connector tools (no prompt to
+ * approve in non-interactive mode). We therefore pre-approve them.
+ *
+ * The connector must still be configured and authenticated in the user's
+ * own Claude CLI — this only grants permission to USE it headlessly. Both
+ * common Notion tool names are allow-listed (the claude.ai connector
+ * `claude_ai_Notion`, and a CLI-added server conventionally named
+ * `notion`). Non-Claude CLIs get the command unchanged.
+ */
+export function withReferenceTools(cmd) {
+    if (!isClaude(cmd.program))
+        return cmd;
+    const allow = [
+        'Read',
+        'Glob',
+        'Grep',
+        'WebFetch',
+        'WebSearch',
+        'mcp__notion__*',
+        'mcp__claude_ai_Notion__*',
+    ].join(' ');
+    return {
+        program: cmd.program,
+        args: [...cmd.args, '--permission-mode', 'acceptEdits', '--allowedTools', allow],
+    };
+}
 /**
  * Decide where a journey's test file should go, based on its type
  * and the config. Falls back to "generated-tests/<area>" when the

package/dist/core/index.js

@@ -4,4 +4,4 @@
  * Currently exposes the package version only.
  * Model, parser, and engines will be added in upcoming steps.
  */
-export const VERSION = '0.3.0';
+export const VERSION = '0.4.0';

package/dist/core/init.js

@@ -29,10 +29,17 @@ export function buildInitPrompt() {
         `  Point each to where that area's tests belong (e.g. in a monorepo,`,
         `  api -> "packages/api/test", web -> "packages/webapp/tests", ops ->`,
         `  "packages/ops/tests"; in a simple app, one area mapping to "tests").`,
-        `- framework: an object mapping each area to its test framework`,
-        `  (e.g. { "api": "jest", "web": "playwright", "ops": "playwright" }),`,
-        `  based on what the project already uses for that area.`,
-        `  the api tests, e.g. "packages/api/test/helpers/seed").`,
+        `  For UI areas, use a plain tests folder (e.g. ".../tests" or`,
+        `  ".../tests/e2e") — do NOT point them at a Cypress folder such as`,
+        `  "cypress/integration", because testforge does not generate Cypress.`,
+        `- framework: an object mapping each area to its test framework.`,
+        `  testforge ONLY generates two kinds of tests, so each value MUST be`,
+        `  exactly "jest" or "playwright" — never "cypress", "mocha", "vitest",`,
+        `  or anything else, EVEN IF the project currently uses one of those.`,
+        `  Choose the closest fit: backend / API / serverless / lambda / worker`,
+        `  areas -> "jest"; UI / web / browser / admin-panel areas ->`,
+        `  "playwright". Example: { "api": "jest", "web": "playwright", "ops":`,
+        `  "playwright", "lambda": "jest" }.`,
         `- testExtension: ".test.ts" or ".test.js" — match what existing`,
         `  tests use, or the project's language (TypeScript vs JavaScript).`,
         `- aiCommand: keep it as "claude -p" unless there is a clear reason`,

package/dist/core/parser.js

@@ -65,8 +65,14 @@ function parseField(line) {
     const required = parts.includes('required');
     return { name, type, required };
 }
-/** Parse a full markdown string into a Journey object. */
-export function parseJourney(markdown) {
+/**
+ * Parse a full markdown string into a Journey object.
+ *
+ * `area` is the journey's docs subfolder (e.g. "api", "ops"), which drives
+ * output location and framework. When omitted (a journey read outside an
+ * area folder), it falls back to the parsed `Type:`.
+ */
+export function parseJourney(markdown, area) {
     const lines = markdown.split('\n').map((l) => l.trim());
     let name = '';
     let type = 'web';
@@ -112,6 +118,7 @@ export function parseJourney(markdown) {
     return {
         id: toId(name),
         name,
+        area: area ?? type,
         type,
         route,
         coverage,

package/dist/core/reference.js

@@ -22,13 +22,13 @@
  * and tuned for the Claude CLI.
  */
 import { execFileSync } from 'node:child_process';
-import { loadConfig, splitCommand, withEditTools } from './config.js';
+import { loadConfig, splitCommand, withReferenceTools } from './config.js';
 /** Where the comparison report is written. */
 export const DIFF_PATH = 'testforge.diff.md';
 const MAP_PATH = 'testforge.md';
-/** Run the configured AI command with read/write/web access. */
+/** Run the configured AI command with read/write/web (+ Notion) access. */
 function runAI(prompt) {
-    const { program, args } = withEditTools(splitCommand(loadConfig().aiCommand));
+    const { program, args } = withReferenceTools(splitCommand(loadConfig().aiCommand));
     const output = execFileSync(program, args, {
         input: prompt,
         encoding: 'utf-8',

package/dist/core/run-generate.js

@@ -56,8 +56,7 @@ function generateValidated(generate, ext) {
  * syntax gate + retry) and falls back to the deterministic basic
  * generator if AI output can't be made valid.
  */
-function buildTest(markdown, useAI, ext, testPath) {
-    const journey = parseJourney(markdown);
+function buildTest(journey, useAI, ext, testPath) {
     if (useAI) {
         const ai = generateValidated(() => generateWithAI(journey, testPath), ext);
         if (ai !== null) {
@@ -116,9 +115,14 @@ export function runGenerate(docsDir, useAI = true, force = false) {
     for (const file of files) {
         const markdown = readFileSync(join(docsDir, file), 'utf-8');
         const hash = hashContent(markdown);
-        const journey = parseJourney(markdown);
+        // The area is the doc's top-level folder (api/web/ops/lambda/...). It
+        // decides where the test goes and which framework is used — NOT the
+        // "Type:" line, which only says UI-vs-endpoint. This keeps ops/lambda
+        // journeys in their own package instead of leaking into web/api.
+        const area = file.split(/[\\/]/)[0] || undefined;
+        const journey = parseJourney(markdown, area);
         // Where this journey's test and seed go.
-        const testDir = testDirForType(config, journey.type);
+        const testDir = testDirForType(config, journey.area);
         const testPath = join(testDir, `${journey.id}${ext}`);
         const seedPath = join(seedDir, `${journey.id}${seedExt}`);
         // Skip if unchanged.
@@ -137,7 +141,7 @@ export function runGenerate(docsDir, useAI = true, force = false) {
         if (collision)
             warnings.push(collision);
         // 1. Test file (syntax-gated before writing).
-        const { content, status } = buildTest(markdown, useAI, ext, testPath);
+        const { content, status } = buildTest(journey, useAI, ext, testPath);
         mkdirSync(dirname(testPath), { recursive: true });
         writeFileSync(testPath, content, 'utf-8');
         // 2. Seed file (only when using AI — basic mode has no seed concept).

package/package.json

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