wopee-mcp 1.23.0 → 1.23.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/build/tools/wopee_create_blank_suite/index.js +1 -1
- package/build/tools/wopee_dispatch_agent/index.js +2 -2
- package/build/tools/wopee_dispatch_analysis/index.js +2 -2
- package/build/tools/wopee_fetch_analysis_suites/index.js +2 -2
- package/build/tools/wopee_fetch_artifact/index.js +2 -2
- package/build/tools/wopee_fetch_executed_test_cases/index.js +2 -2
- package/build/tools/wopee_generate_artifact/index.js +2 -2
- package/build/tools/wopee_update_artifact/index.js +2 -2
- package/package.json +1 -1
|
@@ -7,7 +7,7 @@ export const wopeeCreateBlankSuite = {
|
|
|
7
7
|
name: ToolName.WOPEE_CREATE_BLANK_SUITE,
|
|
8
8
|
config: {
|
|
9
9
|
title: "Create blank analysis suite",
|
|
10
|
-
description: "Create a
|
|
10
|
+
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.",
|
|
11
11
|
},
|
|
12
12
|
handler: async () => {
|
|
13
13
|
try {
|
|
@@ -8,8 +8,8 @@ import { withRetry } from "../../utils/withRetry.js";
|
|
|
8
8
|
export const wopeeDispatchAgent = {
|
|
9
9
|
name: ToolName.WOPEE_DISPATCH_AGENT,
|
|
10
10
|
config: {
|
|
11
|
-
title: "Dispatch agent",
|
|
12
|
-
description: "
|
|
11
|
+
title: "Dispatch autonomous testing agent",
|
|
12
|
+
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.",
|
|
13
13
|
inputSchema: WopeeDispatchAgentInputSchema.shape,
|
|
14
14
|
},
|
|
15
15
|
handler: async (input) => {
|
|
@@ -8,8 +8,8 @@ import { ToolName } from "../shared/types.js";
|
|
|
8
8
|
export const wopeeDispatchAnalysis = {
|
|
9
9
|
name: ToolName.WOPEE_DISPATCH_ANALYSIS,
|
|
10
10
|
config: {
|
|
11
|
-
title: "Dispatch analysis",
|
|
12
|
-
description: "Create and dispatch
|
|
11
|
+
title: "Dispatch analysis crawl",
|
|
12
|
+
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.",
|
|
13
13
|
inputSchema: WopeeDispatchAnalysisInputSchema.shape,
|
|
14
14
|
},
|
|
15
15
|
handler: async (input) => {
|
|
@@ -6,8 +6,8 @@ import { FetchAnalysisSuites } from "../shared/gql-queries.js";
|
|
|
6
6
|
export const wopeeFetchAnalysisSuites = {
|
|
7
7
|
name: ToolName.WOPEE_FETCH_ANALYSIS_SUITES,
|
|
8
8
|
config: {
|
|
9
|
-
title: "
|
|
10
|
-
description: "
|
|
9
|
+
title: "List analysis suites",
|
|
10
|
+
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.",
|
|
11
11
|
},
|
|
12
12
|
handler: async () => {
|
|
13
13
|
try {
|
|
@@ -4,8 +4,8 @@ import { fetchArtifact } from "../shared/handlers.js";
|
|
|
4
4
|
export const wopeeFetchArtifact = {
|
|
5
5
|
name: ToolName.WOPEE_FETCH_ARTIFACT,
|
|
6
6
|
config: {
|
|
7
|
-
title: "Fetch
|
|
8
|
-
description: "
|
|
7
|
+
title: "Fetch test artifacts",
|
|
8
|
+
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.",
|
|
9
9
|
inputSchema: FetchArtifactHandlerInputSchema.shape,
|
|
10
10
|
},
|
|
11
11
|
handler: async (input) => await fetchArtifact(input),
|
|
@@ -7,8 +7,8 @@ import { requestClient } from "../../utils/requestClient.js";
|
|
|
7
7
|
export const wopeeFetchExecutedTestCases = {
|
|
8
8
|
name: ToolName.WOPEE_FETCH_EXECUTED_TEST_CASES,
|
|
9
9
|
config: {
|
|
10
|
-
title: "Fetch
|
|
11
|
-
description: "
|
|
10
|
+
title: "Fetch test execution results",
|
|
11
|
+
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.",
|
|
12
12
|
inputSchema: WopeeFetchExecutedTestCasesInputSchema.shape,
|
|
13
13
|
},
|
|
14
14
|
handler: async (input) => {
|
|
@@ -4,8 +4,8 @@ import { generateAIDataFile } from "../shared/handlers.js";
|
|
|
4
4
|
export const wopeeGenerateArtifact = {
|
|
5
5
|
name: ToolName.WOPEE_GENERATE_ARTIFACT,
|
|
6
6
|
config: {
|
|
7
|
-
title: "Generate
|
|
8
|
-
description: "Generate AI
|
|
7
|
+
title: "Generate test artifacts",
|
|
8
|
+
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.",
|
|
9
9
|
inputSchema: GenerateAIDataHandlerInputSchema.shape,
|
|
10
10
|
},
|
|
11
11
|
handler: async (input) => await generateAIDataFile(input),
|
|
@@ -4,8 +4,8 @@ import { updateArtifact } from "../shared/handlers.js";
|
|
|
4
4
|
export const wopeeUpdateArtifact = {
|
|
5
5
|
name: ToolName.WOPEE_UPDATE_ARTIFACT,
|
|
6
6
|
config: {
|
|
7
|
-
title: "Update
|
|
8
|
-
description: "Update
|
|
7
|
+
title: "Update test artifacts",
|
|
8
|
+
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.",
|
|
9
9
|
inputSchema: UpdateArtifactHandlerInputSchema.shape,
|
|
10
10
|
},
|
|
11
11
|
handler: async (input) => await updateArtifact(input),
|
package/package.json
CHANGED