Develop

.github/prompts/crt-to-provar.prompt.md

@@ -0,0 +1,35 @@
+---
+mode: agent
+description: Convert a CRT (Copado Robotic Testing) test into a Provar XML test case using the Provar MCP tools for corpus grounding and validation
+---
+
+You are a Provar test migration expert. Migrate the CRT test below to Provar.
+
+## Source format — CRT
+
+CRT is a keyword-driven framework built on Robot Framework (QEditor-authored):
+
+- `ClickText <label>` → click an element by visible label
+- `TypeText <field> <value>` → type into a field
+- `VerifyText <text>` → assert text is present on the page
+- `SelectDropdown <field> <value>` → choose a picklist option
+- `OpenBrowser <url>` → open browser / Salesforce login
+
+Robot Framework sections: `*** Keywords ***` = reusable blocks, `*** Test Cases ***` = one file per test.
+
+## Migration workflow
+
+1. **Get examples** — call `provar.qualityhub.examples.retrieve` with keywords that describe the test scenario (e.g. "create account", "close opportunity"). Use the returned XML examples as the sole reference for Provar format and step patterns.
+   If the response has `"count": 0` with a `"warning"` field (API unavailable or not configured), fall back: read the `provar://docs/step-reference` MCP resource for step types and attribute formats, then continue with generation based on that reference.
+2. **Generate** — produce valid Provar XML that captures the intent of the source test, based on the retrieved examples. Omit login/browser setup — Provar handles that via Connection Manager.
+3. **Write** — save the XML to the `tests/` directory in the Provar project.
+4. **Validate** — call `provar.testcase.validate` on the saved file. Fix any errors and re-validate until clean.
+5. **Report** — summarise what was migrated and flag any unmappable steps as `<!-- TODO: manual step — <original QWord> -->`.
+
+## CRT Source
+
+Paste your CRT test here (QWord steps or `.robot` file):
+
+```
+[PASTE CRT TEST HERE]
+```

.github/prompts/playwright-to-provar.prompt.md

@@ -0,0 +1,39 @@
+---
+mode: agent
+description: Convert a Playwright test (TypeScript/JavaScript) into a Provar XML test case using the Provar MCP tools for corpus grounding and validation
+---
+
+You are a Provar test migration expert. Migrate the Playwright test below to Provar.
+
+## Source format — Playwright
+
+Common patterns to recognise:
+
+- `page.goto(url)` / login fixture → Salesforce login
+- `getByLabel(label).click()` → click by visible label
+- `getByRole('button', {name}).click()` → click by button name
+- `getByLabel(label).fill(value)` → fill a field by label
+- `locator(selector).fill(value)` → fill by XPath/CSS
+- `locator.selectOption(value)` → choose a picklist option
+- `expect(locator).toHaveValue(val)` → assert a field value
+- `expect(locator).toBeVisible()` → assert element is visible
+- `expect(page).toContainText(text)` → assert text on page
+- `page.waitForLoadState()` / `waitForSelector()` → wait conditions
+- `beforeEach` → test setup including login
+
+## Migration workflow
+
+1. **Get examples** — call `provar.qualityhub.examples.retrieve` with keywords describing the test scenario (e.g. "create contact", "close opportunity"). Use the returned XML examples as the sole reference for Provar format and step patterns.
+   If the response has `"count": 0` with a `"warning"` field (API unavailable or not configured), fall back: read the `provar://docs/step-reference` MCP resource for step types and attribute formats, then continue with generation based on that reference.
+2. **Generate** — produce valid Provar XML based on the retrieved examples. Omit login/navigation setup — Provar handles Salesforce sessions via Connection Manager.
+3. **Write** — save the XML to the `tests/` directory in the Provar project.
+4. **Validate** — call `provar.testcase.validate` on the saved file. Fix any errors and re-validate until clean.
+5. **Report** — summarise what was migrated and flag any unmappable steps as `<!-- TODO: manual step — <original code> -->`.
+
+## Playwright Source
+
+Paste your Playwright test here (TypeScript or JavaScript):
+
+```typescript
+[PASTE PLAYWRIGHT TEST HERE]
+```

.github/prompts/selenium-to-provar.prompt.md

@@ -0,0 +1,36 @@
+---
+mode: agent
+description: Convert a Selenium WebDriver test (Java/Python/JS) into a Provar XML test case using the Provar MCP tools for corpus grounding and validation
+---
+
+You are a Provar test migration expert. Migrate the Selenium test below to Provar.
+
+## Source format — Selenium WebDriver
+
+Common patterns to recognise:
+
+- `driver.get(url)` / `navigate().to()` → Salesforce login
+- `findElement(By.linkText/name).click()` → click by visible label
+- `findElement(...).sendKeys(value)` → type into a field
+- `Select.selectByVisibleText(val)` → choose a picklist option
+- `findElement(...).getText()` + assertion → verify a field value
+- `WebDriverWait` / `ExpectedConditions` → wait for element
+- `@Before` / `setUp()` → test setup including login
+- `@After` / `tearDown()` → cleanup
+
+## Migration workflow
+
+1. **Get examples** — call `provar.qualityhub.examples.retrieve` with keywords describing the test scenario (e.g. "create opportunity", "convert lead"). Use the returned XML examples as the sole reference for Provar format and step patterns.
+   If the response has `"count": 0` with a `"warning"` field (API unavailable or not configured), fall back: read the `provar://docs/step-reference` MCP resource for step types and attribute formats, then continue with generation based on that reference.
+2. **Generate** — produce valid Provar XML based on the retrieved examples. Omit browser/login setup — Provar handles Salesforce sessions via Connection Manager.
+3. **Write** — save the XML to the `tests/` directory in the Provar project.
+4. **Validate** — call `provar.testcase.validate` on the saved file. Fix any errors and re-validate until clean.
+5. **Report** — summarise what was migrated and flag any unmappable steps as `<!-- TODO: manual step — <original code> -->`.
+
+## Selenium Source
+
+Paste your Selenium test here (Java, Python, or JavaScript):
+
+```
+[PASTE SELENIUM TEST HERE]
+```

README.md

@@ -73,7 +73,7 @@ claude mcp add provar -s user -- sf provar mcp start --allowed-paths /path/to/yo
 
 > **Windows (Claude Desktop):** Use `sf.cmd` instead of `sf` if the server fails to start.
 
-📖 **[docs/mcp.md](https://github.com/ProvarTesting/provardx-cli/blob/main/docs/mcp.md) — full setup, all 35+ tools, troubleshooting.**
+📖 **[docs/mcp.md](https://github.com/ProvarTesting/provardx-cli/blob/main/docs/mcp.md) — full setup, all 35+ tools, 7 MCP prompts, troubleshooting.**
 
 ---