@yasserkhanorg/e2e-agents 0.5.13 → 0.5.14

package/dist/agent/ai_mapping.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"ai_mapping.d.ts","sourceRoot":"","sources":["../../src/agent/ai_mapping.ts"],"names":[],"mappings":"AAMA,OAAO,KAAK,EAAC,UAAU,EAAC,MAAM,eAAe,CAAC;AAC9C,OAAO,KAAK,EAAC,qBAAqB,EAAC,MAAM,aAAa,CAAC;AACvD,OAAO,KAAK,EAAC,YAAY,EAAE,QAAQ,EAAC,MAAM,YAAY,CAAC;AA4BvD,MAAM,WAAW,eAAe;IAC5B,OAAO,EAAE,OAAO,CAAC;IACjB,IAAI,EAAE,OAAO,CAAC;IACd,QAAQ,EAAE,MAAM,CAAC;IACjB,WAAW,EAAE,MAAM,CAAC;IACpB,YAAY,EAAE,MAAM,CAAC;IACrB,QAAQ,EAAE,YAAY,EAAE,CAAC;IACzB,QAAQ,EAAE,MAAM,EAAE,CAAC;CACtB;AAyWD,wBAAsB,iBAAiB,CACnC,OAAO,EAAE,MAAM,EACf,SAAS,EAAE,MAAM,EACjB,MAAM,EAAE,qBAAqB,EAC7B,KAAK,EAAE,UAAU,EAAE,EACnB,KAAK,EAAE,QAAQ,EAAE,GAClB,OAAO,CAAC,eAAe,CAAC,CA4O1B"}
+{"version":3,"file":"ai_mapping.d.ts","sourceRoot":"","sources":["../../src/agent/ai_mapping.ts"],"names":[],"mappings":"AAMA,OAAO,KAAK,EAAC,UAAU,EAAC,MAAM,eAAe,CAAC;AAC9C,OAAO,KAAK,EAAC,qBAAqB,EAAC,MAAM,aAAa,CAAC;AACvD,OAAO,KAAK,EAAC,YAAY,EAAE,QAAQ,EAAC,MAAM,YAAY,CAAC;AA4BvD,MAAM,WAAW,eAAe;IAC5B,OAAO,EAAE,OAAO,CAAC;IACjB,IAAI,EAAE,OAAO,CAAC;IACd,QAAQ,EAAE,MAAM,CAAC;IACjB,WAAW,EAAE,MAAM,CAAC;IACpB,YAAY,EAAE,MAAM,CAAC;IACrB,QAAQ,EAAE,YAAY,EAAE,CAAC;IACzB,QAAQ,EAAE,MAAM,EAAE,CAAC;CACtB;AA4WD,wBAAsB,iBAAiB,CACnC,OAAO,EAAE,MAAM,EACf,SAAS,EAAE,MAAM,EACjB,MAAM,EAAE,qBAAqB,EAC7B,KAAK,EAAE,UAAU,EAAE,EACnB,KAAK,EAAE,QAAQ,EAAE,GAClB,OAAO,CAAC,eAAe,CAAC,CA2O1B"}

package/dist/agent/ai_mapping.js

@@ -249,8 +249,11 @@ function selectCandidateTests(flows, tests, maxCandidateTests) {
                         continue;
                     }
                     const matched = fallbackKws.filter((k) => haystack.includes(k));
-                    if (matched.length < fallbackKws.length) {
-                        continue; // all tokens must appear in at least one test title
+                    // For 3+ tokens, n-1 must match (allows one absent word like "view");
+                    // for 1-2 tokens all must match.
+                    const required = fallbackKws.length >= 3 ? fallbackKws.length - 1 : fallbackKws.length;
+                    if (matched.length < required) {
+                        continue;
                     }
                     fallbackCandidates.push({ path: testPath, score: matched.length, matchedKeywords: matched });
                 }
@@ -418,12 +421,11 @@ async function mapAITestsToFlows(appRoot, testsRoot, config, flows, tests) {
         'Rules:',
         '- Keep at most 5 tests per flow.',
         '- Use exact flowId values from FLOWS.',
-        '- Map a test when you have clear evidence it covers the flow — from the file path OR from test titles in the content. Behavioral coverage via test titles is sufficient even when the filename does not exactly match the flow (e.g. search_user_post_spec.js covers search_messages if its titles assert searching for messages). Generic subsystem similarity without behavioral evidence is not enough.',
+        '- Map a test when you have behavioral evidence it covers the flow scenario, from the file path OR from test titles in the content. A file named search_user_post_spec.js with titles like "search for message by keyword" covers search_messages. Generic subsystem similarity without behavioral evidence is not enough.',
         '- A flow may only map to tests listed under FLOW_CANDIDATE_SIGNALS for that flow.',
-        '- Treat single-keyword or broad subsystem overlap as insufficient evidence.',
-        '- If the candidate path overlap is weak or ambiguous, return tests: [].',
-        '- If unsure for a flow, return tests: [].',
-        '- For EVERY flow (whether or not tests were found), return missingScenarios with 3-5 key user-facing test scenarios that must be covered. Write each as a short imperative statement starting with a verb (e.g. "Search for a message by keyword and verify results appear"). For mapped flows, focus on what the existing tests do NOT cover; for unmapped flows, describe the core scenarios a new test should include.',
+        '- When a flow has 3 or more candidate tests that collectively cover its behavioral domain (e.g. multiple search specs for search_messages, multiple messaging specs for view_post_in_channel), map all of them. Collective coverage across multiple files counts as full coverage.',
+        '- Only return tests: [] when NO candidate file has clear behavioral overlap to the flow.',
+        '- missingScenarios: for flows with no test mappings (tests: []), list 3-5 core scenarios that a new test must cover. For flows WITH test mappings, ONLY list scenarios that are genuinely absent from ALL mapped tests combined — if the mapped tests collectively cover the core user-facing scenarios well, return missingScenarios: []. Do not invent edge-case gaps for well-covered flows.',
         '',
         `FLOWS (${prioritizedFlows.length}):`,
         JSON.stringify(prioritizedFlows.map((flow) => ({

package/dist/esm/agent/ai_mapping.js

@@ -246,8 +246,11 @@ function selectCandidateTests(flows, tests, maxCandidateTests) {
                         continue;
                     }
                     const matched = fallbackKws.filter((k) => haystack.includes(k));
-                    if (matched.length < fallbackKws.length) {
-                        continue; // all tokens must appear in at least one test title
+                    // For 3+ tokens, n-1 must match (allows one absent word like "view");
+                    // for 1-2 tokens all must match.
+                    const required = fallbackKws.length >= 3 ? fallbackKws.length - 1 : fallbackKws.length;
+                    if (matched.length < required) {
+                        continue;
                     }
                     fallbackCandidates.push({ path: testPath, score: matched.length, matchedKeywords: matched });
                 }
@@ -415,12 +418,11 @@ export async function mapAITestsToFlows(appRoot, testsRoot, config, flows, tests
         'Rules:',
         '- Keep at most 5 tests per flow.',
         '- Use exact flowId values from FLOWS.',
-        '- Map a test when you have clear evidence it covers the flow — from the file path OR from test titles in the content. Behavioral coverage via test titles is sufficient even when the filename does not exactly match the flow (e.g. search_user_post_spec.js covers search_messages if its titles assert searching for messages). Generic subsystem similarity without behavioral evidence is not enough.',
+        '- Map a test when you have behavioral evidence it covers the flow scenario, from the file path OR from test titles in the content. A file named search_user_post_spec.js with titles like "search for message by keyword" covers search_messages. Generic subsystem similarity without behavioral evidence is not enough.',
         '- A flow may only map to tests listed under FLOW_CANDIDATE_SIGNALS for that flow.',
-        '- Treat single-keyword or broad subsystem overlap as insufficient evidence.',
-        '- If the candidate path overlap is weak or ambiguous, return tests: [].',
-        '- If unsure for a flow, return tests: [].',
-        '- For EVERY flow (whether or not tests were found), return missingScenarios with 3-5 key user-facing test scenarios that must be covered. Write each as a short imperative statement starting with a verb (e.g. "Search for a message by keyword and verify results appear"). For mapped flows, focus on what the existing tests do NOT cover; for unmapped flows, describe the core scenarios a new test should include.',
+        '- When a flow has 3 or more candidate tests that collectively cover its behavioral domain (e.g. multiple search specs for search_messages, multiple messaging specs for view_post_in_channel), map all of them. Collective coverage across multiple files counts as full coverage.',
+        '- Only return tests: [] when NO candidate file has clear behavioral overlap to the flow.',
+        '- missingScenarios: for flows with no test mappings (tests: []), list 3-5 core scenarios that a new test must cover. For flows WITH test mappings, ONLY list scenarios that are genuinely absent from ALL mapped tests combined — if the mapped tests collectively cover the core user-facing scenarios well, return missingScenarios: []. Do not invent edge-case gaps for well-covered flows.',
         '',
         `FLOWS (${prioritizedFlows.length}):`,
         JSON.stringify(prioritizedFlows.map((flow) => ({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yasserkhanorg/e2e-agents",
-  "version": "0.5.13",
+  "version": "0.5.14",
   "description": "Pluggable LLM provider library for AI-powered test automation. Use Claude, Ollama, or your own LLM. Integrate with Playwright, Jest, or any test framework. MCP server for test agents, cost tracking, and hybrid provider mode.",
   "main": "dist/index.js",
   "module": "dist/esm/index.js",