wopee-mcp 1.21.0 → 1.23.1

package/README.md

@@ -298,7 +298,7 @@ Dispatches an autonomous testing agent to execute test cases for a selected suit
   - `testCases` - Array of test case objects to execute, each containing:
     - `testCaseId` - The ID of the test case
     - `userStoryId` - The ID of the associated user story
-- **Returns:** Success message indicating the agent has been dispatched
+- **Returns:** Array of executed test case objects with their initial execution state (uuid, executionStatus, agentReportStatus, codeReportStatus, etc.)
 
 **Example Usage:**
 
@@ -306,6 +306,27 @@ Dispatches an autonomous testing agent to execute test cases for a selected suit
 Dispatch agent for my latest suite's user story US001 and test case TC003
 ```
 
+### Test Results
+
+#### `wopee_fetch_executed_test_cases`
+
+Fetches executed test cases and their results for a given analysis suite. Use this to check the status and reports of dispatched agent runs.
+
+- **Parameters:**
+  - `suiteUuid` - The UUID of the analysis suite to fetch results for
+  - `analysisIdentifier` _(optional)_ - Analysis identifier to narrow results (e.g. `A068`)
+- **Returns:** Array of results grouped by user story, each containing executed test cases with execution status, agent report, agent report status, code report, and code report status
+
+**Example Usage:**
+
+```
+Fetch test results for suite <suiteUuid>
+```
+
+```
+Show me the executed test cases for my latest analysis suite
+```
+
 ## Typical Workflow
 
 1. **Start with a suite:**
@@ -326,6 +347,20 @@ Dispatch agent for my latest suite's user story US001 and test case TC003
 4. **Run tests:**
    - Use `wopee_dispatch_agent` to execute test cases with the autonomous testing agent
 
+5. **Check results:**
+   - Use `wopee_fetch_executed_test_cases` to check the status and reports of dispatched agent runs
+   - Or use the `fetch-test-results` prompt for a formatted summary of all test results
+
+## Available Prompts
+
+### `fetch-project-summary`
+
+Fetches analysis suites and their user stories/test cases, then displays a formatted summary with two markdown tables: a suite overview and a detailed test case breakdown.
+
+### `fetch-test-results`
+
+Fetches analysis suites and their executed test case results, then displays formatted markdown tables showing execution status, agent report status, and code report status for each test case. Also surfaces failed report details.
+
 ## Notes
 
 - Most tools require a `suiteUuid`. Always start by fetching or creating a suite.

package/build/prompts/fetch_test_results/index.js

@@ -0,0 +1,65 @@
+import { PromptName } from "../shared/types.js";
+export const fetchTestResults = {
+    name: PromptName.FETCH_TEST_RESULTS,
+    config: {
+        title: "Fetch test results",
+        description: "Fetch and display test execution results for analysis suites",
+    },
+    handler: () => ({
+        messages: [
+            {
+                role: "user",
+                content: {
+                    type: "text",
+                    text: `Please, fetch my analysis suites using 'wopee_fetch_analysis_suites' tool. If there are more than 5 suites, ask the user to select which suite(s) they want to see results for.
+
+          Then, for each selected suite, fetch the executed test cases using 'wopee_fetch_executed_test_cases' tool with the suite's uuid and analysisIdentifier.
+
+          After fetching all of the necessary data, summarize and display readable markdown tables as an output in the same chat conversation. Do NOT create, write, or save any files to disk - only display the formatted tables in your response.
+
+          Display the following tables:
+
+          1. **Suite Overview Table** - one row per suite showing:
+            - Suite name
+            - Analysis identifier
+            - Execution status
+            - Suite running status
+
+          ### Example:
+          | Suite Name | Identifier | Execution Status | Running Status |
+          |------------|------------|------------------|----------------|
+          | Analysis - A068 | A068 | FINISHED | IDLE |
+          | Analysis - A067 | A067 | IN_PROGRESS | IN_PROGRESS |
+
+          ___
+
+          2. **Test Case Results Table** - for each suite that has executed test cases:
+            - Suite name
+            - User story ID
+            - Test case ID
+            - Execution status
+            - Agent report status (PASSED/FAILED or N/A)
+            - Code report status (PASSED/FAILED or N/A)
+
+          ### Example:
+          | Suite Name | User Story | Test Case | Execution | Agent Status | Code Status |
+          |------------|------------|-----------|-----------|--------------|-------------|
+          | Analysis - A068 | US001 | TC001 | FINISHED | PASSED | PASSED |
+          | | US001 | TC002 | FINISHED | PASSED | FAILED |
+          | | US002 | TC001 | FINISHED | FAILED | N/A |
+          | Analysis - A067 | US001 | TC001 | IN_PROGRESS | N/A | N/A |
+
+          ___
+
+          3. If any test case has a FAILED agent or code report status, display the report content below the tables under a "Failed Reports" section, showing the suite name, test case ID, and the report text.
+
+          ## Important Notes:
+            - If a test case's executionStatus is IN_PROGRESS, note that results are not yet available.
+            - Use "N/A" for report statuses that are null (not yet available).
+            - Group test cases by user story within each suite.
+          `,
+                },
+            },
+        ],
+    }),
+};

package/build/prompts/index.js

@@ -1,2 +1,3 @@
 import { fetchProjectSummary } from "./fetch_project_summary/index.js";
-export const PROMPTS = [fetchProjectSummary];
+import { fetchTestResults } from "./fetch_test_results/index.js";
+export const PROMPTS = [fetchProjectSummary, fetchTestResults];

package/build/prompts/shared/types.js

@@ -1,4 +1,5 @@
 export var PromptName;
 (function (PromptName) {
     PromptName["FETCH_PROJECT_SUMMARY"] = "fetch-project-summary";
+    PromptName["FETCH_TEST_RESULTS"] = "fetch-test-results";
 })(PromptName || (PromptName = {}));

package/build/tools/index.js

@@ -5,9 +5,11 @@ import { wopeeDispatchAgent } from "./wopee_dispatch_agent/index.js";
 import { wopeeDispatchAnalysis } from "./wopee_dispatch_analysis/index.js";
 import { wopeeCreateBlankSuite } from "./wopee_create_blank_suite/index.js";
 import { wopeeFetchAnalysisSuites } from "./wopee_fetch_analysis_suites/index.js";
+import { wopeeFetchExecutedTestCases } from "./wopee_fetch_executed_test_cases/index.js";
 export const TOOLS = [
     wopeeCreateBlankSuite,
     wopeeFetchAnalysisSuites,
+    wopeeFetchExecutedTestCases,
     wopeeDispatchAnalysis,
     wopeeDispatchAgent,
     wopeeFetchArtifact,

package/build/tools/shared/gql-queries.js

@@ -155,6 +155,28 @@ export const GenerateReusableTestCaseSteps = `
     generateReusableTestCaseSteps(input: $input)
   }
 `;
+export const FetchExecutedTestCases = `
+  query FetchExecutedTestCases($input: FetchExecutedTestCasesInput!) {
+    fetchExecutedTestCases(input: $input) {
+      userStoryId
+      executedTestCases {
+        uuid
+        suiteUuid
+        analysisSuiteUuid
+        analysisIdentifier
+        userStoryId
+        testCaseId
+        executionStatus
+        agentReport
+        agentReportStatus
+        codeReport
+        codeReportStatus
+        createdAt
+        updatedAt
+      }
+    }
+  }
+`;
 export const CreateBlankAnalysisSuite = `
   mutation CreateBlankAnalysisSuite($projectUuid: ID!) {
     createBlankAnalysisSuite(projectUuid: $projectUuid) {

package/build/tools/shared/types.js

@@ -2,6 +2,7 @@ export var ToolName;
 (function (ToolName) {
     ToolName["WOPEE_CREATE_BLANK_SUITE"] = "wopee_create_blank_suite";
     ToolName["WOPEE_FETCH_ANALYSIS_SUITES"] = "wopee_fetch_analysis_suites";
+    ToolName["WOPEE_FETCH_EXECUTED_TEST_CASES"] = "wopee_fetch_executed_test_cases";
     ToolName["WOPEE_DISPATCH_ANALYSIS"] = "wopee_dispatch_analysis";
     ToolName["WOPEE_DISPATCH_AGENT"] = "wopee_dispatch_agent";
     ToolName["WOPEE_FETCH_ARTIFACT"] = "wopee_fetch_artifact";
@@ -56,3 +57,8 @@ export var GenerationStatus;
     GenerationStatus["FINISHED"] = "FINISHED";
     GenerationStatus["FAILED"] = "FAILED";
 })(GenerationStatus || (GenerationStatus = {}));
+export var ReportStatus;
+(function (ReportStatus) {
+    ReportStatus["PASSED"] = "PASSED";
+    ReportStatus["FAILED"] = "FAILED";
+})(ReportStatus || (ReportStatus = {}));

package/build/tools/wopee_create_blank_suite/index.js

@@ -7,7 +7,7 @@ export const wopeeCreateBlankSuite = {
     name: ToolName.WOPEE_CREATE_BLANK_SUITE,
     config: {
         title: "Create blank analysis suite",
-        description: "Create a blank analysis suite for a project",
+        description: "Create a new empty analysis suite in the current project. Use this as the first step when starting a new testing workflow — the returned suite UUID is required by generate, fetch, update, and dispatch tools. Takes no input parameters; uses the project configured via WOPEE_PROJECT_UUID. Returns the created suite object including its UUID and metadata.",
     },
     handler: async () => {
         try {

package/build/tools/wopee_dispatch_agent/index.js

@@ -8,8 +8,8 @@ import { withRetry } from "../../utils/withRetry.js";
 export const wopeeDispatchAgent = {
     name: ToolName.WOPEE_DISPATCH_AGENT,
     config: {
-        title: "Dispatch agent",
-        description: "Dispatch agent testing for selected suite's test cases. Note: there is a 10-second per-project rate limit between dispatches; concurrent calls will auto-retry with backoff.",
+        title: "Dispatch autonomous testing agent",
+        description: "Run an autonomous AI testing agent on specific test cases within a suite. The agent navigates the web app, executes test steps, captures screenshots, and reports pass/fail results. Requires a suite UUID and test case ID (e.g. TC001) with its parent user story ID (e.g. US001). Use wopee_generate_artifact first to create test cases, then this tool to execute them. Rate limit: 10 seconds between dispatches per project; concurrent calls auto-retry with backoff. Returns executed test case results including status and agent report.",
         inputSchema: WopeeDispatchAgentInputSchema.shape,
     },
     handler: async (input) => {
@@ -32,7 +32,7 @@ export const wopeeDispatchAgent = {
                 content: [
                     {
                         type: "text",
-                        text: "Agent dispatched successfully",
+                        text: JSON.stringify(result.dispatchAgent, null, 2),
                     },
                 ],
             };

package/build/tools/wopee_dispatch_analysis/index.js

@@ -8,8 +8,8 @@ import { ToolName } from "../shared/types.js";
 export const wopeeDispatchAnalysis = {
     name: ToolName.WOPEE_DISPATCH_ANALYSIS,
     config: {
-        title: "Dispatch analysis",
-        description: "Create and dispatch analysis/crawling suite for a project. Note: there is a 10-second per-project rate limit between dispatches; concurrent calls will auto-retry with backoff.",
+        title: "Dispatch analysis crawl",
+        description: "Create a new analysis suite and dispatch an AI crawling agent to explore and analyze a web application. The agent autonomously navigates the app starting from a given URL, discovers pages, and builds a sitemap. Optionally accepts login credentials, cookie preferences, custom variables, and additional instructions to guide the crawl. Use this instead of wopee_create_blank_suite when you want to auto-analyze a web app in one step. Rate limit: 10 seconds between dispatches per project; concurrent calls auto-retry with backoff. Returns the created analysis suite.",
         inputSchema: WopeeDispatchAnalysisInputSchema.shape,
     },
     handler: async (input) => {

package/build/tools/wopee_fetch_analysis_suites/index.js

@@ -6,8 +6,8 @@ import { FetchAnalysisSuites } from "../shared/gql-queries.js";
 export const wopeeFetchAnalysisSuites = {
     name: ToolName.WOPEE_FETCH_ANALYSIS_SUITES,
     config: {
-        title: "Fetch Analysis Suites",
-        description: "Fetch project's analysis suites from Woopee",
+        title: "List analysis suites",
+        description: "List all analysis suites in the current project. Returns an array of suites with their UUIDs, names, types, and statuses. Use this to find existing suites before generating content or dispatching agents. Takes no input parameters; uses the project configured via WOPEE_PROJECT_UUID. Each suite UUID can be passed to other tools like wopee_generate_artifact, wopee_fetch_artifact, or wopee_dispatch_agent.",
     },
     handler: async () => {
         try {

package/build/tools/wopee_fetch_artifact/index.js

@@ -4,8 +4,8 @@ import { fetchArtifact } from "../shared/handlers.js";
 export const wopeeFetchArtifact = {
     name: ToolName.WOPEE_FETCH_ARTIFACT,
     config: {
-        title: "Fetch file(artifact)",
-        description: "Fetch suite's file(artifact) for selected project",
+        title: "Fetch test artifacts",
+        description: "Retrieve test artifacts from a suite. Supported types: APP_CONTEXT (application description), GENERAL_USER_STORIES (user stories without test cases), USER_STORIES (user stories with test cases), PLAYWRIGHT_CODE (Playwright test code for a specific test case — requires identifier like 'US004:TC006'), PROJECT_CONTEXT (project-level context). Use after wopee_generate_artifact to review test artifacts, or to retrieve existing artifacts for editing with wopee_update_artifact.",
         inputSchema: FetchArtifactHandlerInputSchema.shape,
     },
     handler: async (input) => await fetchArtifact(input),

package/build/tools/wopee_fetch_executed_test_cases/factory.js

@@ -0,0 +1,13 @@
+import { getConfig } from "../../utils/getConfig.js";
+export const createFetchExecutedTestCasesInput = (input) => {
+    const { WOPEE_PROJECT_UUID } = getConfig();
+    if (!WOPEE_PROJECT_UUID)
+        throw new Error("WOPEE_PROJECT_UUID is not set");
+    return {
+        projectUuid: WOPEE_PROJECT_UUID,
+        analysisSuiteUuid: input.suiteUuid,
+        ...(input.analysisIdentifier
+            ? { analysisIdentifier: input.analysisIdentifier }
+            : {}),
+    };
+};

package/build/tools/wopee_fetch_executed_test_cases/index.js

@@ -0,0 +1,43 @@
+import { WopeeFetchExecutedTestCasesInputSchema, FetchExecutedTestCasesInputSchema, } from "./schema.js";
+import { ToolName } from "../shared/types.js";
+import { _parseError } from "../shared/helpers.js";
+import { createFetchExecutedTestCasesInput } from "./factory.js";
+import { FetchExecutedTestCases } from "../shared/gql-queries.js";
+import { requestClient } from "../../utils/requestClient.js";
+export const wopeeFetchExecutedTestCases = {
+    name: ToolName.WOPEE_FETCH_EXECUTED_TEST_CASES,
+    config: {
+        title: "Fetch test execution results",
+        description: "Retrieve the results of test cases that have been executed by the autonomous agent. Returns each test case with its execution status (IN_PROGRESS, FINISHED, FAILED), agent report, and code report. Use this after wopee_dispatch_agent to check whether tests passed or failed and to review detailed findings. Requires the suite UUID; optionally accepts an analysis identifier (e.g. A068) to filter results.",
+        inputSchema: WopeeFetchExecutedTestCasesInputSchema.shape,
+    },
+    handler: async (input) => {
+        try {
+            const factoryInput = createFetchExecutedTestCasesInput(input);
+            const parsedInput = FetchExecutedTestCasesInputSchema.parse(factoryInput);
+            const result = await requestClient(FetchExecutedTestCases, {
+                input: parsedInput,
+            });
+            if (!result?.fetchExecutedTestCases)
+                return {
+                    content: [
+                        {
+                            type: "text",
+                            text: "Failed to fetch executed test cases: no data returned",
+                        },
+                    ],
+                };
+            return {
+                content: [
+                    {
+                        type: "text",
+                        text: JSON.stringify(result.fetchExecutedTestCases, null, 2),
+                    },
+                ],
+            };
+        }
+        catch (error) {
+            return _parseError(error);
+        }
+    },
+};

package/build/tools/wopee_fetch_executed_test_cases/schema.js

@@ -0,0 +1,18 @@
+import { z } from "zod";
+export const WopeeFetchExecutedTestCasesInputSchema = z.object({
+    suiteUuid: z
+        .string({
+        description: "UUID of the analysis suite to fetch executed test cases for",
+    })
+        .min(1, "Suite UUID is required"),
+    analysisIdentifier: z
+        .string({
+        description: "Analysis identifier of the suite (ex. A068). Can be found in the analysis suite data.",
+    })
+        .optional(),
+});
+export const FetchExecutedTestCasesInputSchema = z.object({
+    projectUuid: z.string().min(1, "Project UUID is required"),
+    analysisSuiteUuid: z.string().min(1, "Suite UUID is required"),
+    analysisIdentifier: z.string().optional(),
+});

package/build/tools/wopee_generate_artifact/index.js

@@ -4,8 +4,8 @@ import { generateAIDataFile } from "../shared/handlers.js";
 export const wopeeGenerateArtifact = {
     name: ToolName.WOPEE_GENERATE_ARTIFACT,
     config: {
-        title: "Generate file(artifact)",
-        description: "Generate AI data file for selected suite",
+        title: "Generate test artifacts",
+        description: "Generate AI-powered test artifacts for a suite. Supported types: APP_CONTEXT (analyze the application and create a description), GENERAL_USER_STORIES (generate user stories from app context), USER_STORIES_WITH_TEST_CASES (generate user stories with detailed test cases), TEST_CASES (generate test cases for existing user stories), TEST_CASE_STEPS (generate step-by-step instructions for test cases), REUSABLE_TEST_CASES (generate reusable/shared test cases), REUSABLE_TEST_CASE_STEPS (generate steps for reusable test cases). Typical workflow: generate APP_CONTEXT first, then USER_STORIES_WITH_TEST_CASES, then use wopee_dispatch_agent to execute them.",
         inputSchema: GenerateAIDataHandlerInputSchema.shape,
     },
     handler: async (input) => await generateAIDataFile(input),

package/build/tools/wopee_update_artifact/index.js

@@ -4,8 +4,8 @@ import { updateArtifact } from "../shared/handlers.js";
 export const wopeeUpdateArtifact = {
     name: ToolName.WOPEE_UPDATE_ARTIFACT,
     config: {
-        title: "Update file",
-        description: "Update file(artifact) in the project",
+        title: "Update test artifacts",
+        description: "Update previously generated content in a suite. Use this to refine user stories, test cases, app context, or Playwright code after reviewing them with wopee_fetch_artifact. Requires the content type (APP_CONTEXT, GENERAL_USER_STORIES, USER_STORIES, PLAYWRIGHT_CODE, or PROJECT_CONTEXT), the suite UUID, and the new content as a string. For PLAYWRIGHT_CODE, also provide the test case identifier (e.g. 'US004:TC006'). This enables an iterative workflow: generate → review → update → dispatch.",
         inputSchema: UpdateArtifactHandlerInputSchema.shape,
     },
     handler: async (input) => await updateArtifact(input),

package/package.json

@@ -4,7 +4,7 @@
   "bin": {
     "wopee-mcp": "./build/index.js"
   },
-  "version": "1.21.0",
+  "version": "1.23.1",
   "mcpName": "io.github.Wopee-io/wopee-mcp",
   "description": "Wopee.io MCP server for autonomous testing platform",
   "main": "./build/index.js",