wopee-mcp 1.30.2 → 1.31.0

package/README.md

@@ -344,6 +344,26 @@ Fetch test results for suite <suiteUuid>
 Show me the executed test cases for my latest analysis suite
 ```
 
+### Reporting
+
+#### `wopee_create_github_issue`
+
+Files a GitHub issue into the repository linked to the current project. Given a failed run's `executedTestCaseUuid`, Wopee.io adds what it knows about that run below your text: the failing step, expected vs actual, the failing step's screenshot and a link to the run in Commander.
+
+- **Parameters:**
+  - `title` - The issue title
+  - `body` _(optional)_ - Markdown, kept verbatim above the run evidence
+  - `labels` _(optional)_ - Labels to apply, e.g. `["bug"]`. GitHub may skip labels the repository doesn't have; the result says which were applied
+  - `executedTestCaseUuid` _(optional)_ - The run to attach evidence from, as shown by `wopee_fetch_recent_executions` or `wopee_dispatch_agent`
+- **Returns:** The issue number and URL, plus notes on anything left out (e.g. a screenshot that could not be uploaded)
+- **Requirements:** The issue is created by the Wopee.io GitHub App and names you in its body. The App's installation needs the **Issues: Read & write** repository permission, and **Contents: Read & write** for the screenshot, which is committed to a separate `wopee-issue-assets` branch. That branch has no shared history with your code and is safe to delete; deleting it only breaks the images in existing issues.
+
+**Example Usage:**
+
+```
+File the failed checkout test as a GitHub issue
+```
+
 ## Typical Workflow
 
 1. **Start with a suite:**
@@ -369,6 +389,9 @@ Show me the executed test cases for my latest analysis suite
    - Use `wopee_fetch_executed_test_cases` to check detailed status and reports for a specific suite
    - Or use the `fetch-test-results` prompt for a formatted summary of all test results
 
+6. **Report failures:**
+   - Use `wopee_create_github_issue` with the failed run's `executedTestCaseUuid` to file it into your repository
+
 ## Available Prompts
 
 ### `fetch-project-summary`

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

@@ -295,11 +295,26 @@ export const FetchRecentExecutedTestCases = `
   }
 `;
 export const CreateGitHubIssue = `
-  mutation CreateGitHubIssue($projectUuid: ID!, $title: String!, $body: String!, $labels: [String!]) {
-    createGitHubIssue(projectUuid: $projectUuid, title: $title, body: $body, labels: $labels) {
+  mutation CreateGitHubIssue(
+    $projectUuid: ID!
+    $title: String!
+    $body: String!
+    $labels: [String!]
+    $executedTestCaseUuid: ID
+  ) {
+    createGitHubIssue(
+      projectUuid: $projectUuid
+      title: $title
+      body: $body
+      labels: $labels
+      executedTestCaseUuid: $executedTestCaseUuid
+    ) {
       url
       number
       title
+      screenshotAttached
+      labelsApplied
+      warnings
     }
   }
 `;

package/build/tools/wopee_create_github_issue/format.js

@@ -0,0 +1,21 @@
+// The text an MCP caller reads back after filing an issue.
+//
+// No runtime imports, which keeps it unit-testable under `node --test`.
+export function formatIssueCreated(issue, { withRunEvidence }) {
+    const lines = [
+        "GitHub issue created successfully:",
+        `- Title: ${issue.title}`,
+        `- Number: #${issue.number}`,
+        `- URL: ${issue.url}`,
+    ];
+    if (issue.labelsApplied?.length) {
+        lines.push(`- Labels: ${issue.labelsApplied.join(", ")}`);
+    }
+    if (withRunEvidence) {
+        lines.push(`- Run evidence: failing step, expected vs actual and the Commander report link added; screenshot ${issue.screenshotAttached ? "attached" : "not attached"}`);
+    }
+    for (const warning of issue.warnings ?? []) {
+        lines.push(`- Note: ${warning}`);
+    }
+    return lines.join("\n");
+}

package/build/tools/wopee_create_github_issue/index.js

@@ -4,21 +4,27 @@ import { requestClient } from "../../utils/requestClient.js";
 import { _parseError } from "../shared/helpers.js";
 import { ToolName } from "../shared/types.js";
 import { CreateGitHubIssue } from "../shared/gql-queries.js";
+import { formatIssueCreated } from "./format.js";
 const InputSchema = z.object({
     title: z.string().describe("The title of the GitHub issue"),
     body: z
         .string()
-        .describe("The body/description of the GitHub issue (supports Markdown)"),
+        .optional()
+        .describe("The body/description of the GitHub issue (supports Markdown). Kept verbatim, above anything Wopee.io adds from the test run."),
     labels: z
         .array(z.string())
         .optional()
         .describe("Optional labels to apply to the issue (e.g., ['bug', 'testing'])"),
+    executedTestCaseUuid: z
+        .string()
+        .optional()
+        .describe("UUID of the executed test case the issue is about (the executedTestCaseUuid shown by wopee_fetch_recent_executions and wopee_dispatch_agent, or uuid in wopee_fetch_executed_test_cases). When set, Wopee.io adds the failing step, expected vs actual, the failing step's screenshot and a link to the run in Commander, so the body only needs your own analysis."),
 });
 export const wopeeCreateGithubIssue = {
     name: ToolName.WOPEE_CREATE_GITHUB_ISSUE,
     config: {
         title: "Create GitHub issue",
-        description: "Create a new GitHub issue in the project's connected repository. Use this to report bugs found during testing, track test failures, or create action items from chat discussions. The issue will be created in the GitHub repository linked to the current project. Requires the project to have GitHub integration configured and WOPEE_PROJECT_UUID to be set.",
+        description: "Create a new GitHub issue in the project's connected repository. Use this to report bugs found during testing, track test failures, or create action items from chat discussions. For a failed test, pass its executedTestCaseUuid so the issue carries the run's evidence (failing step, expected vs actual, screenshot, report link). The issue is created by the Wopee.io GitHub App and names the requester in its body. Requires a GitHub repository linked to the project and WOPEE_PROJECT_UUID to be set.",
         inputSchema: InputSchema.shape,
     },
     handler: async (input) => {
@@ -33,15 +39,18 @@ export const wopeeCreateGithubIssue = {
             const result = await requestClient(CreateGitHubIssue, {
                 projectUuid: WOPEE_PROJECT_UUID,
                 title: input.title,
-                body: input.body,
+                body: input.body ?? "",
                 labels: input.labels || [],
+                ...(input.executedTestCaseUuid && {
+                    executedTestCaseUuid: input.executedTestCaseUuid,
+                }),
             });
             if (!result?.createGitHubIssue)
                 return {
                     content: [
                         {
                             type: "text",
-                            text: "Failed to create GitHub issue. Make sure the project has GitHub integration configured.",
+                            text: "Failed to create GitHub issue. Make sure the project has a GitHub repository linked.",
                         },
                     ],
                 };
@@ -49,7 +58,9 @@ export const wopeeCreateGithubIssue = {
                 content: [
                     {
                         type: "text",
-                        text: `GitHub issue created successfully:\n- Title: ${result.createGitHubIssue.title}\n- Number: #${result.createGitHubIssue.number}\n- URL: ${result.createGitHubIssue.url}`,
+                        text: formatIssueCreated(result.createGitHubIssue, {
+                            withRunEvidence: !!input.executedTestCaseUuid,
+                        }),
                     },
                 ],
             };

package/build/tools/wopee_fetch_recent_executions/index.js

@@ -52,6 +52,8 @@ export const wopeeFetchRecentExecutions = {
                 // INCOMPLETE on top, and reporting it as FAILED tells the user their app is broken.
                 const status = tc.agentReportStatus ?? tc.executionStatus;
                 lines.push(`- ${tc.userStoryId}:${tc.testCaseId} [${tc.analysisIdentifier}] → ${status} (${tc.updatedAt})`);
+                // The handle wopee_create_github_issue takes to attach this run's evidence.
+                lines.push(`  executedTestCaseUuid: ${tc.uuid}`);
                 // Any report, not only a FINISHED run's: an incomplete run's report is what names the
                 // infrastructure error behind it.
                 if (tc.agentReport) {

package/package.json

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