@skyramp/mcp 0.0.64-rc.14 → 0.0.64-rc.16
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.
|
@@ -32,8 +32,8 @@ Use those recommendations as your baseline. Only add or remove tests that the us
|
|
|
32
32
|
|
|
33
33
|
## Step 1: Analyze
|
|
34
34
|
|
|
35
|
-
|
|
36
|
-
If all changed files are non-application
|
|
35
|
+
The diff is at \`${diffFile}\`. Do NOT read it manually with the Read tool — \`skyramp_analyze_changes\` (step 1 below) reads and parses it for you. Call it immediately.
|
|
36
|
+
If \`skyramp_analyze_changes\` reports all changed files are non-application → skip to Step 4 (Submit Report) with empty arrays.
|
|
37
37
|
|
|
38
38
|
Otherwise: proceed to the numbered steps below.`;
|
|
39
39
|
return `<TITLE>${prTitle}</TITLE>
|
|
@@ -182,10 +182,7 @@ Generate a net-new test only for resources with no existing test coverage. Use a
|
|
|
182
182
|
1. \`browser_navigate\` **directly** to the deepest relevant URL (e.g. \`/orders/1/edit\` instead of \`/\` then \`/orders\` then \`/orders/1\`). Avoid multi-hop navigation — go straight to the page you need.
|
|
183
183
|
2. \`browser_snapshot\` once to see the page (ARIA tree)
|
|
184
184
|
3. Perform interactions (\`browser_click\`, \`browser_type\`, \`browser_select_option\`). Only call \`browser_snapshot\` again when you need new element refs — do NOT snapshot between every click.
|
|
185
|
-
4. **Add assertions with \`browser_assert\`** — MANDATORY. Call multiple \`browser_assert\` in the **same tool call batch** when checking independent elements.
|
|
186
|
-
- \`type: "visible"\` — verify an element exists
|
|
187
|
-
- \`type: "text"\` — verify element text matches expected value
|
|
188
|
-
- \`type: "value"\` — verify an input field's value
|
|
185
|
+
4. **Add assertions with \`browser_assert\`** — MANDATORY. Refer to the tool's own parameter schema for valid \`type\` values. Call multiple \`browser_assert\` in the **same tool call batch** when checking independent elements.
|
|
189
186
|
You MUST add at least one \`browser_assert\` per page navigated to. If you navigate to 2 different pages in a trace, assert on both — not just the first one. Each assertion should verify the primary expected content of that page (e.g. heading, key element).
|
|
190
187
|
5. \`skyramp_export_zip\` with an **absolute** output path: \`<repositoryPath>/.skyramp/<test_name>_trace.zip\`
|
|
191
188
|
6. \`skyramp_ui_test_generation\` with \`playwrightInput\` set to the **absolute** path of the exported zip
|