@zibby/core 0.3.6 → 0.3.8

package/templates/generate-test-cases/state.js

@@ -0,0 +1,54 @@
+/**
+ * State schema for the generate-test-cases standalone template.
+ *
+ * Same shape as code-analysis (workspace + repos + ticketContext) PLUS
+ * a `codeImplementation` field — the diff this template generates tests
+ * for. In code-analysis that field is produced by the upstream
+ * generate_code node; here, the user provides it directly.
+ */
+
+import { z } from 'zod';
+
+export const generateTestCasesStateSchema = z.object({
+  workspace: z.string().describe('Local workspace path'),
+
+  repos: z.array(z.object({
+    name: z.string(),
+    url: z.string().url(),
+    path: z.string().optional(),
+    branch: z.string().default('main'),
+    isPrimary: z.boolean().default(false),
+  })).optional().describe('Repository configurations (cloned by setup node so the LLM can explore routing/components)'),
+
+  ticketContext: z.object({
+    key: z.string().regex(/^[A-Z]+-\d+$/, 'Invalid ticket format (expected PROJ-123)').optional(),
+    ticketKey: z.string().optional(),
+    summary: z.string().min(1).describe('Ticket summary/title'),
+    description: z.any().optional().describe('Ticket description (string or ADF object)'),
+    acceptanceCriteria: z.string().optional(),
+    type: z.string().optional(),
+    priority: z.string().optional(),
+    labels: z.array(z.string()).optional(),
+    components: z.array(z.string()).optional(),
+  }).describe('Jira/ticket context — informs test priorities + naming'),
+
+  // The new direct-input field that distinguishes this standalone template
+  // from code-analysis. In code-analysis this comes from generate_code's
+  // output; here the user supplies it (e.g. from `git diff` of a PR they
+  // want tests for).
+  codeImplementation: z.object({
+    diff: z.string().describe('Unified-diff string of the changes'),
+    changedFiles: z.array(z.string()).describe('List of file paths touched'),
+  }).describe('Code changes to generate tests for'),
+
+  githubToken: z.string().optional().describe('GitHub PAT (needed only if repos[].url requires auth)'),
+  model: z.string().default('auto').describe('AI model to use'),
+  nodeConfigs: z.record(z.string(), z.any()).optional().describe('Per-node configuration overrides (e.g. extractContext for test credentials)'),
+});
+
+// Clean isolation: this schema declares ONLY what the template's nodes
+// actually need. No EXECUTION_ID / PROGRESS_QUEUE_URL / SQS_AUTH_TOKEN
+// / PROJECT_API_TOKEN — those were legacy analysis-UI plumbing fields
+// and the new templates run via the standard `workflow run` /
+// `workflow trigger` cloud pipeline, which has its own progress
+// reporting outside the state object.

package/templates/index.js

@@ -12,6 +12,18 @@ export const TEMPLATES = {
     description: 'Complete browser test automation workflow with title generation, live execution, and script generation',
     path: join(__dirname, 'browser-test-automation'),
     default: true,
+    // Suggested slug for `zibby workflow new <slug> -t <name>`. Used in
+    // the `template list` scaffold hint so the printed command is
+    // copy-paste-ready instead of `your-workflow-name`. Users can still
+    // pick anything they want at scaffold time.
+    defaultSlug: 'browser-tests',
+    // Runtime deps the scaffolded copy needs in addition to @zibby/core.
+    // graph.mjs now imports state.js which `import { z } from 'zod'`s
+    // directly, so the user's package.json must declare zod or the
+    // scaffolded workflow fails on first import.
+    deps: {
+      zod: '^3.23.0',
+    },
     features: [
       'Preflight analysis: extract title + assertion checklist from spec',
       'Execute test live with AI + browser (Claude or Cursor)',
@@ -19,6 +31,47 @@ export const TEMPLATES = {
       'Real-time streaming output',
       'Video recording of browser sessions'
     ]
+  },
+  'code-analysis': {
+    name: 'code-analysis',
+    displayName: 'Code Analysis (Ticket → Code + Tests)',
+    description: 'Multi-node workflow that analyzes a Jira ticket against a code repo, generates code changes, and emits test cases',
+    path: join(__dirname, 'code-analysis'),
+    defaultSlug: 'ticket-analyzer',
+    // Runtime deps the scaffolded copy needs in addition to @zibby/core.
+    // Merged into the generated package.json so `npm install` works
+    // without manual edits. Browser-test doesn't declare any because
+    // its nodes only depend on @zibby/core.
+    deps: {
+      axios: '^1.6.0',
+      handlebars: '^4.7.8',
+      zod: '^3.23.0',
+    },
+    features: [
+      'Clone repos + snapshot git baseline',
+      'LLM analysis of ticket against codebase (canProceed gate)',
+      'Conditional routing: skip code-gen if ticket is invalid',
+      'Generate scoped code changes',
+      'Generate test cases covering the changes',
+      'Customizable prompts in prompts/*.md'
+    ]
+  },
+  'generate-test-cases': {
+    name: 'generate-test-cases',
+    displayName: 'Generate Test Cases (Diff → Test Specs)',
+    description: 'Standalone slice — takes an existing code diff and generates plain-English test specifications for it. Skips ticket-analysis and code-gen.',
+    path: join(__dirname, 'generate-test-cases'),
+    defaultSlug: 'tests-from-diff',
+    deps: {
+      zod: '^3.23.0',
+    },
+    features: [
+      'Two-node graph: setup → generate_test_cases',
+      'Takes a PR diff directly as state input (no upstream code-gen needed)',
+      'LLM explores codebase routing/components for accurate test steps',
+      'Emits 4-8 prioritized test specs (Critical/High/Medium/Low)',
+      'Plain-English test steps — runnable by AI agents'
+    ]
   }
 };