SWTBot Probe Scripts
Use this skill to create or update JSON probes for com.microsoft.copilot.eclipse.swtbot.test.
Probes drive the workbench through SWTBot actions and run as Tycho tests; no Java is compiled per test case.
Quick start
Create one focused JSON script at
com.microsoft.copilot.eclipse.swtbot.test/probe-scripts/<plan-slug>-<tc-id>.json.
Start by settling the workbench and opening the view under test:
[
{ "action": "waitForIdle" },
{ "action": "screenshot", "id": "01-startup" },
{ "action": "showView", "idRef": "com.microsoft.copilot.eclipse.ui.chat.ChatView" },
{ "action": "waitForIdle" },
{ "action": "screenshot", "id": "02-chat-open" }
]
Add user-level steps only, such as click, typeIn, clearElement, pressKey,
invokeCommand, waitFor, waitForMethod, assertExists, screenshot, or
dumpUi. Prefer widgetId locators for widgets the plugin owns.
Run from the repository root:
./mvnw clean verify -Dprobe.script=probe-scripts/<name>.json
Use root clean verify as the default. Tycho can reuse stale bundle jars
when only the SWTBot module is run, making source edits appear ignored. Use
xvfb-run -a on Linux headless.
Read com.microsoft.copilot.eclipse.swtbot.test/target/probe-results/results.json,
workspace.log, screenshots/, and ui-dumps/.
If -Dprobe.script is unset, ProbeRunner skips itself so ordinary ./mvnw verify runs are unaffected.
Authoring workflow
- Convert one scenario/test case into one probe. Split unrelated behaviors so each failure screenshot has one meaning.
- Drive the UI the way a user does.
invokeCommand is allowed for registered Eclipse command IDs; do not call
OSGi services, private methods, or test-only shortcuts.
- Pair screenshots with machine-checked assertions. Screenshots never fail a step;
assertExists, waitFor, and
waitForMethod decide pass/fail.
- Wait for asynchronous UI state before acting. For chat, wait for the
model-picker selected model before Send,
then wait for user-turn and model-info-label.
- When a locator fails, insert
dumpUi before the failure and inspect ui-dumps/*.xml for widget class names and
SWTBot widget IDs.
- For unauthenticated chat probes, assert the "Sign in to GitHub" UI. Do not poll internal auth managers.
Chat send skeleton
[
{ "action": "waitForIdle" },
{ "action": "showView", "idRef": "com.microsoft.copilot.eclipse.ui.chat.ChatView" },
{ "action": "waitFor", "locator": { "by": "styledText" }, "timeoutSec": 30 },
{ "action": "clearElement", "locator": { "by": "styledText" } },
{ "action": "typeIn", "locator": { "by": "styledText" }, "text": "hello" },
{ "action": "waitForMethod", "locator": { "by": "widgetId", "value": "model-picker" },
"method": "getSelectedItemId", "timeoutSec": 60 },
{ "action": "click", "locator": { "by": "buttonWithTooltip", "tooltip": "Send" } },
{ "action": "waitFor", "locator": { "by": "widgetId", "value": "user-turn" }, "timeoutSec": 30 },
{ "action": "waitFor", "locator": { "by": "cssClass", "value": "model-info-label" }, "timeoutSec": 120 },
{ "action": "assertExists", "locator": { "by": "widgetId", "value": "copilot-turn" } },
{ "action": "screenshot", "id": "agent-response" }
]
Pass/fail judgment
A probe passes only when Maven exits 0 and results.json has "failed": 0.
On failure, inspect the failed step message, FAILED-stepNN-*.png, nearest ui-dumps/*.xml, and workspace.log.
Extending probes
The vocabulary lives in com.microsoft.copilot.eclipse.swtbot.test/src/.../probe/.
Add UI-level primitives in ProbeStep, Locator, and StepExecutor, then update REFERENCE.md.
See REFERENCE.md for action/locator tables, platform notes, result queries, troubleshooting, and current stable widget IDs.
1---2name: ui-action3description: Authors and validates SWTBot JSON probe scripts for GitHub Copilot for Eclipse UI flows against a real Eclipse workbench. Use when creating or updating probe-scripts, converting test plans to UI probes, validating end-to-end Eclipse UI behavior, or troubleshooting ProbeRunner failures.4metadata:5 source: https://skillmd.com/skills/microsoft/ui-action6---78# SWTBot Probe Scripts910Use this skill to create or update JSON probes for `com.microsoft.copilot.eclipse.swtbot.test`.11Probes drive the workbench through SWTBot actions and run as Tycho tests; no Java is compiled per test case.1213## Quick start14151. Create one focused JSON script at16 `com.microsoft.copilot.eclipse.swtbot.test/probe-scripts/<plan-slug>-<tc-id>.json`.172. Start by settling the workbench and opening the view under test:1819 ```json20 [21 { "action": "waitForIdle" },22 { "action": "screenshot", "id": "01-startup" },23 { "action": "showView", "idRef": "com.microsoft.copilot.eclipse.ui.chat.ChatView" },24 { "action": "waitForIdle" },25 { "action": "screenshot", "id": "02-chat-open" }26 ]27 ```28293. Add user-level steps only, such as `click`, `typeIn`, `clearElement`, `pressKey`,30 `invokeCommand`, `waitFor`, `waitForMethod`, `assertExists`, `screenshot`, or31 `dumpUi`. Prefer `widgetId` locators for widgets the plugin owns.324. Run from the repository root:3334 ```bash35 ./mvnw clean verify -Dprobe.script=probe-scripts/<name>.json36 ```3738 Use root `clean verify` as the default. Tycho can reuse stale bundle jars39 when only the SWTBot module is run, making source edits appear ignored. Use40 `xvfb-run -a` on Linux headless.415. Read `com.microsoft.copilot.eclipse.swtbot.test/target/probe-results/results.json`,42 `workspace.log`, `screenshots/`, and `ui-dumps/`.4344If `-Dprobe.script` is unset, `ProbeRunner` skips itself so ordinary `./mvnw verify` runs are unaffected.4546## Authoring workflow4748- Convert one scenario/test case into one probe. Split unrelated behaviors so each failure screenshot has one meaning.49- Drive the UI the way a user does. `invokeCommand` is allowed for registered Eclipse command IDs; do not call50 OSGi services, private methods, or test-only shortcuts.51- Pair screenshots with machine-checked assertions. Screenshots never fail a step; `assertExists`, `waitFor`, and52 `waitForMethod` decide pass/fail.53- Wait for asynchronous UI state before acting. For chat, wait for the `model-picker` selected model before Send,54 then wait for `user-turn` and `model-info-label`.55- When a locator fails, insert `dumpUi` before the failure and inspect `ui-dumps/*.xml` for widget class names and56 SWTBot widget IDs.57- For unauthenticated chat probes, assert the "Sign in to GitHub" UI. Do not poll internal auth managers.5859## Chat send skeleton6061```json62[63 { "action": "waitForIdle" },64 { "action": "showView", "idRef": "com.microsoft.copilot.eclipse.ui.chat.ChatView" },65 { "action": "waitFor", "locator": { "by": "styledText" }, "timeoutSec": 30 },66 { "action": "clearElement", "locator": { "by": "styledText" } },67 { "action": "typeIn", "locator": { "by": "styledText" }, "text": "hello" },68 { "action": "waitForMethod", "locator": { "by": "widgetId", "value": "model-picker" },69 "method": "getSelectedItemId", "timeoutSec": 60 },70 { "action": "click", "locator": { "by": "buttonWithTooltip", "tooltip": "Send" } },71 { "action": "waitFor", "locator": { "by": "widgetId", "value": "user-turn" }, "timeoutSec": 30 },72 { "action": "waitFor", "locator": { "by": "cssClass", "value": "model-info-label" }, "timeoutSec": 120 },73 { "action": "assertExists", "locator": { "by": "widgetId", "value": "copilot-turn" } },74 { "action": "screenshot", "id": "agent-response" }75]76```7778## Pass/fail judgment7980A probe passes only when Maven exits `0` and `results.json` has `"failed": 0`.81On failure, inspect the failed step message, `FAILED-stepNN-*.png`, nearest `ui-dumps/*.xml`, and `workspace.log`.8283## Extending probes8485The vocabulary lives in `com.microsoft.copilot.eclipse.swtbot.test/src/.../probe/`.86Add UI-level primitives in `ProbeStep`, `Locator`, and `StepExecutor`, then update [REFERENCE.md](REFERENCE.md).8788See [REFERENCE.md](REFERENCE.md) for action/locator tables, platform notes, result queries, troubleshooting, and current stable widget IDs.