k11-selenium-qa-mcp 0.1.0__tar.gz

k11_selenium_qa_mcp-0.1.0/.gitignore

@@ -0,0 +1,9 @@
+.venv/
+venv/
+__pycache__/
+*.egg-info/
+dist/
+build/
+.pytest_cache/
+.tmp*
+.qa-mcp/auth/

k11_selenium_qa_mcp-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 K11 Software Solutions
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

k11_selenium_qa_mcp-0.1.0/PKG-INFO

@@ -0,0 +1,209 @@
+Metadata-Version: 2.5
+Name: k11-selenium-qa-mcp
+Version: 0.1.0
+Summary: MCP server and Claude Code plugin for Selenium QA: verified locators, user story to pytest, and self-healing locators with an audit trail.
+Project-URL: Homepage, https://github.com/K11-Software-Solutions/k11techlab-selenium-qa-mcp
+Project-URL: Issues, https://github.com/K11-Software-Solutions/k11techlab-selenium-qa-mcp/issues
+Author: K11 Software Solutions
+License-Expression: MIT
+License-File: LICENSE
+Keywords: claude,mcp,pytest,qa,selenium,self-healing,test-automation
+Classifier: Development Status :: 4 - Beta
+Classifier: Framework :: Pytest
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.10
+Requires-Dist: mcp<2,>=1.20
+Requires-Dist: selenium>=4.27
+Provides-Extra: dev
+Requires-Dist: pytest-timeout>=2; extra == 'dev'
+Requires-Dist: pytest>=8; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# k11 Selenium QA — MCP server & Claude Code plugin
+
+<!-- mcp-name: io.github.K11-Software-Solutions/selenium-qa -->
+
+**Self-healing Selenium tests with an audit trail. No vendor lock-in, no rewrite to Playwright.**
+
+Most Selenium suites break the same way: someone renames an id, and dozens of `find_element(By.ID, ...)` calls fail overnight. AI assistants can write Selenium tests, but they guess locators, and healing tools usually patch things at runtime without telling you what changed. This MCP server gives the assistant facts instead of guesses, and gives your team a reviewable record of every fix:
+
+- **Verified locators.** It opens the real page in Selenium and returns locators that match exactly one element, most stable first: `data-testid`, a stable `id`, `name`, link text, `aria-label`, then text-based XPath.
+- **Story → pytest.** It turns "As a… I want… so that…", Gherkin scenarios or acceptance-criteria bullets into a pytest + Selenium skeleton: one test per scenario, explicit waits, and a `driver` fixture if you don't have one.
+- **Structured test runs.** It runs your pytest suite and reports, for each failure, the exact locator Selenium could not find, the line that asked for it, and the page the browser was on.
+- **Self-healing with evidence.** When the UI changes, it finds the element the test meant and suggests a verified replacement, with a confidence score, the reasons and the runner-up.
+- **Healing in CI.** `heal-ci` applies only confident fixes, edits your tests *and Page Objects*, re-runs them, reverts anything that still fails, and opens a pull request whose description is the audit report.
+
+Works with **Claude Code** (as a plugin with `/story-to-test` and `/heal-tests`), **Claude Desktop**, and any MCP client. Python 3.10+, Selenium 4.
+
+---
+
+## See it heal in CI
+
+The demo app's account page was redesigned: ids renamed, a "View returns" button added next to "View orders", "Edit profile" renamed to "Account settings", the cart message reworded and the page title changed. The Selenium suite uses a Page Object:
+
+```python
+class AccountPage:
+    VIEW_ORDERS = (By.ID, "view-orders")
+    OPEN_CART = (By.ID, "cart-btn")
+```
+
+`k11-selenium-qa-mcp heal-ci --apply` produced this pull-request description (trimmed):
+
+> **1 healed and verified**, 0 suggested, 1 reverted, 1 needs review, 0 not found, 1 failure not caused by locators.
+>
+> | Test | Where | Old locator | New locator | Confidence | Runner-up | Re-run |
+> |---|---|---|---|---|---|---|
+> | test_shows_my_orders | tests/pages/account_page.py:7 | `(By.ID, "view-orders")` | `(By.ID, "orders-toggle")` | 82% | `(By.ID, "returns-toggle")` (59%) | passed |
+>
+> Why: name matches, role matches, text matches, type matches, tag matches; classes similar (43%).
+>
+> **Needs a person:** "Edit profile" → best candidate "Account settings" at 45%, not confident enough to change. `(By.ID, "cart-btn")` healed at 85%, but the test still failed because the cart message changed too, so the change was **reverted**.
+>
+> **Not caused by locators:** `test_has_the_account_title` (the page title changed). Untouched: it may be a real bug.
+
+It picked "View orders" over the look-alike "View returns", fixed it where it lives (the Page Object, not the test), and refused to guess where a person should decide.
+
+## Tools
+
+| Tool | What it does |
+|---|---|
+| `explore_page` | Opens a URL and lists elements with Selenium locators verified to match exactly one element. |
+| `check_locator` | Counts what a locator matches on a page (1 = good) and whether it's visible. |
+| `parse_user_story` | User story → scenarios + a pytest/Selenium skeleton (and a `conftest.py` if you need one). |
+| `write_test` | Writes `test_*.py`, `*_test.py` or `conftest.py` into `tests/`. Refuses other paths; won't overwrite unless asked. |
+| `run_tests` | Runs pytest and returns per-test results with the failing locator, its line and the page. |
+| `capture_baseline` | While tests pass, fingerprints the element each locator matches (`.qa-mcp/baselines.json`). |
+| `heal_locator` | Finds the intended element after a UI change and suggests a verified replacement. |
+| `save_login_state` | Logs in once with a few steps and saves cookies + localStorage for the other tools. |
+
+Locators are written the way your code writes them: `(By.ID, "email")`, `driver.find_element(By.XPATH, "//button[...]")`, or `(By.CSS_SELECTOR, "[data-testid='save']")`.
+
+Prompt: **`story_to_selenium`**, a guided workflow from story to passing test.
+
+## How self-healing works
+
+1. **Baseline.** While tests pass, `capture_baseline` records each element's fingerprint: role, accessible name, test id, id, `name`, type, label, placeholder, classes, text and href.
+2. **Detect.** `run_tests` loads a small pytest plugin that notes the last locator Selenium could not find, including inside `WebDriverWait` and expected conditions, and the page the browser was on.
+3. **Match.** `heal_locator` scores every visible element on the current page against the fingerprint, with exact matching for stable attributes and fuzzy, synonym-aware matching for text and ids ("Sign in" ≈ "Log in", `btn` ≈ `button`).
+4. **Verify.** The best match gets the most stable Selenium locator that matches exactly one element on the live page.
+5. **Decide.** `healed` only when confidence is at least 0.55 and clearly ahead of the runner-up; otherwise `needs_review` with candidates, or `not_found`. Without a baseline it falls back to what the locator implies, and says so.
+
+Commit `.qa-mcp/baselines.json`. Do **not** commit `.qa-mcp/auth/` (saved logins); `save_login_state` adds it to `.gitignore`.
+
+## Pages behind a login and multi-step flows
+
+Every page tool accepts a `session`:
+
+```json
+{
+  "url": "https://shop.example.com/account",
+  "session": {
+    "storage_state": ".qa-mcp/auth/default.json",
+    "steps": [
+      { "action": "click", "locator": "(By.LINK_TEXT, \"My orders\")" },
+      { "action": "wait_for", "locator": "(By.CSS_SELECTOR, \"[data-testid='order-history']\")" }
+    ]
+  }
+}
+```
+
+- **`storage_state`**: cookies and localStorage saved by `save_login_state`, in the same JSON format Playwright uses. It must be inside the project.
+- **`steps`**: `goto`, `click`, `fill`, `press`, `select`, `check`, `uncheck`, `wait_for`, up to 25, with explicit waits.
+- **Secrets stay out of prompts and logs.** Write `"value": "${ENV:APP_PASSWORD}"`. Results show the placeholder; literal fill values are masked as `•••`.
+
+## Healing in CI, with an audit trail
+
+```bash
+k11-selenium-qa-mcp heal-ci --apply
+```
+
+1. Runs your pytest suite with the locator-recording plugin.
+2. For each locator failure, opens the page the test was on (logging in first if `.qa-mcp/heal.config.json` says how) and heals against the committed baseline.
+3. Applies a change only when confidence is at least **0.7** (`--min-confidence`) and clearly ahead of the runner-up. It edits every place the locator literal appears: tests, Page Objects, helpers.
+4. **Re-runs the affected tests and reverts any change whose test still fails**, keeping the others.
+5. Leaves failures that aren't about locators alone.
+6. Writes `heal-report.md` (the pull-request body) and `heal-report.json` (full evidence), plus GitHub Actions outputs.
+
+Without `--apply` it's a dry run. Copy [`docs/heal-locators.yml`](docs/heal-locators.yml) into `.github/workflows/` to run it nightly and open the pull request, and [`docs/heal.config.example.json`](docs/heal.config.example.json) to `.qa-mcp/heal.config.json`.
+
+## Install
+
+Requires Python 3.10+ and Chrome (or Edge/Firefox with `QA_MCP_BROWSER=edge|firefox`). Selenium Manager downloads the matching driver automatically.
+
+### Claude Code: plugin (recommended)
+
+Adds the MCP tools plus `/story-to-test` and `/heal-tests` (needs [uv](https://docs.astral.sh/uv/)):
+
+```text
+/plugin marketplace add K11-Software-Solutions/k11techlab-selenium-qa-mcp
+/plugin install selenium-qa@k11-selenium-qa
+```
+
+### Claude Code: MCP server only
+
+From your test project's folder:
+
+```bash
+claude mcp add selenium-qa -- uvx --from git+https://github.com/K11-Software-Solutions/k11techlab-selenium-qa-mcp k11-selenium-qa-mcp
+```
+
+Or with pip: `pip install git+https://github.com/K11-Software-Solutions/k11techlab-selenium-qa-mcp`, then `claude mcp add selenium-qa -- k11-selenium-qa-mcp`.
+
+### Claude Desktop and other MCP clients
+
+```json
+{
+  "mcpServers": {
+    "selenium-qa": {
+      "command": "uvx",
+      "args": ["--from", "git+https://github.com/K11-Software-Solutions/k11techlab-selenium-qa-mcp", "k11-selenium-qa-mcp"],
+      "env": { "QA_MCP_ROOT": "/path/to/your/tests/project" }
+    }
+  }
+}
+```
+
+The server works on the project in `QA_MCP_ROOT`, or the current directory. Tests run with the project's own interpreter: `QA_MCP_PYTHON`, else `.venv`/`venv` in the project, else the server's Python. That environment needs `pytest` and `selenium`.
+
+## Try the demo
+
+```bash
+python demo/server.py --version v1      # http://127.0.0.1:8765/login.html (alex@example.com / correct-horse)
+python demo/server.py --version v2      # the redesign
+```
+
+## Safety
+
+- **Locators are parsed, never `eval`'d.** Only `By.<STRATEGY>, "<string>"` forms (and the WebDriver strategy names) are accepted.
+- **Writes are confined to `tests/`** (`write_test`) or to the exact locator literal (`heal-ci`), which is found with Python's tokenizer, so comments and other code are never touched. Line endings are preserved.
+- **Tests run without a shell,** with the project's interpreter.
+- **Healing only suggests** in the MCP tools. `heal-ci --apply` changes code only for confident, verified fixes, and every change is in a pull request for review.
+
+## How it compares
+
+| | Runtime self-healing tools | k11 Selenium QA |
+|---|---|---|
+| Where the fix goes | Patched in memory during the run | Your source (tests and Page Objects), in a pull request |
+| Evidence | Logs | Confidence, reasons and runner-up in a report |
+| If the fix is wrong | Test passes against the wrong element | Re-run must pass, or the change is reverted |
+| Lock-in | Proxy, agent or SDK in your test run | A pytest plugin used only while healing; nothing in your code depends on it |
+
+## Development
+
+```bash
+python -m venv .venv && .venv/Scripts/pip install -e ".[dev]"   # bin/pip on macOS/Linux
+pytest        # unit, real-browser, MCP protocol and heal-ci tests (27)
+```
+
+## Roadmap
+
+- Java (JUnit 5 / TestNG) and C# (NUnit) test projects
+- Healing for chained `find_element` calls and `find_elements(...)[n]`
+- Visual (screenshot) fingerprints as an extra signal
+- PyPI release (`uvx k11-selenium-qa-mcp`)
+
+---
+
+Built by [K11 Software Solutions](https://k11softwaresolutions.com). Part of the K11 Tech Lab agentic QA series, alongside [k11 Playwright QA](https://github.com/K11-Software-Solutions/k11techlab-playwright-qa-mcp). MIT licensed.

k11_selenium_qa_mcp-0.1.0/README.md

@@ -0,0 +1,186 @@
+# k11 Selenium QA — MCP server & Claude Code plugin
+
+<!-- mcp-name: io.github.K11-Software-Solutions/selenium-qa -->
+
+**Self-healing Selenium tests with an audit trail. No vendor lock-in, no rewrite to Playwright.**
+
+Most Selenium suites break the same way: someone renames an id, and dozens of `find_element(By.ID, ...)` calls fail overnight. AI assistants can write Selenium tests, but they guess locators, and healing tools usually patch things at runtime without telling you what changed. This MCP server gives the assistant facts instead of guesses, and gives your team a reviewable record of every fix:
+
+- **Verified locators.** It opens the real page in Selenium and returns locators that match exactly one element, most stable first: `data-testid`, a stable `id`, `name`, link text, `aria-label`, then text-based XPath.
+- **Story → pytest.** It turns "As a… I want… so that…", Gherkin scenarios or acceptance-criteria bullets into a pytest + Selenium skeleton: one test per scenario, explicit waits, and a `driver` fixture if you don't have one.
+- **Structured test runs.** It runs your pytest suite and reports, for each failure, the exact locator Selenium could not find, the line that asked for it, and the page the browser was on.
+- **Self-healing with evidence.** When the UI changes, it finds the element the test meant and suggests a verified replacement, with a confidence score, the reasons and the runner-up.
+- **Healing in CI.** `heal-ci` applies only confident fixes, edits your tests *and Page Objects*, re-runs them, reverts anything that still fails, and opens a pull request whose description is the audit report.
+
+Works with **Claude Code** (as a plugin with `/story-to-test` and `/heal-tests`), **Claude Desktop**, and any MCP client. Python 3.10+, Selenium 4.
+
+---
+
+## See it heal in CI
+
+The demo app's account page was redesigned: ids renamed, a "View returns" button added next to "View orders", "Edit profile" renamed to "Account settings", the cart message reworded and the page title changed. The Selenium suite uses a Page Object:
+
+```python
+class AccountPage:
+    VIEW_ORDERS = (By.ID, "view-orders")
+    OPEN_CART = (By.ID, "cart-btn")
+```
+
+`k11-selenium-qa-mcp heal-ci --apply` produced this pull-request description (trimmed):
+
+> **1 healed and verified**, 0 suggested, 1 reverted, 1 needs review, 0 not found, 1 failure not caused by locators.
+>
+> | Test | Where | Old locator | New locator | Confidence | Runner-up | Re-run |
+> |---|---|---|---|---|---|---|
+> | test_shows_my_orders | tests/pages/account_page.py:7 | `(By.ID, "view-orders")` | `(By.ID, "orders-toggle")` | 82% | `(By.ID, "returns-toggle")` (59%) | passed |
+>
+> Why: name matches, role matches, text matches, type matches, tag matches; classes similar (43%).
+>
+> **Needs a person:** "Edit profile" → best candidate "Account settings" at 45%, not confident enough to change. `(By.ID, "cart-btn")` healed at 85%, but the test still failed because the cart message changed too, so the change was **reverted**.
+>
+> **Not caused by locators:** `test_has_the_account_title` (the page title changed). Untouched: it may be a real bug.
+
+It picked "View orders" over the look-alike "View returns", fixed it where it lives (the Page Object, not the test), and refused to guess where a person should decide.
+
+## Tools
+
+| Tool | What it does |
+|---|---|
+| `explore_page` | Opens a URL and lists elements with Selenium locators verified to match exactly one element. |
+| `check_locator` | Counts what a locator matches on a page (1 = good) and whether it's visible. |
+| `parse_user_story` | User story → scenarios + a pytest/Selenium skeleton (and a `conftest.py` if you need one). |
+| `write_test` | Writes `test_*.py`, `*_test.py` or `conftest.py` into `tests/`. Refuses other paths; won't overwrite unless asked. |
+| `run_tests` | Runs pytest and returns per-test results with the failing locator, its line and the page. |
+| `capture_baseline` | While tests pass, fingerprints the element each locator matches (`.qa-mcp/baselines.json`). |
+| `heal_locator` | Finds the intended element after a UI change and suggests a verified replacement. |
+| `save_login_state` | Logs in once with a few steps and saves cookies + localStorage for the other tools. |
+
+Locators are written the way your code writes them: `(By.ID, "email")`, `driver.find_element(By.XPATH, "//button[...]")`, or `(By.CSS_SELECTOR, "[data-testid='save']")`.
+
+Prompt: **`story_to_selenium`**, a guided workflow from story to passing test.
+
+## How self-healing works
+
+1. **Baseline.** While tests pass, `capture_baseline` records each element's fingerprint: role, accessible name, test id, id, `name`, type, label, placeholder, classes, text and href.
+2. **Detect.** `run_tests` loads a small pytest plugin that notes the last locator Selenium could not find, including inside `WebDriverWait` and expected conditions, and the page the browser was on.
+3. **Match.** `heal_locator` scores every visible element on the current page against the fingerprint, with exact matching for stable attributes and fuzzy, synonym-aware matching for text and ids ("Sign in" ≈ "Log in", `btn` ≈ `button`).
+4. **Verify.** The best match gets the most stable Selenium locator that matches exactly one element on the live page.
+5. **Decide.** `healed` only when confidence is at least 0.55 and clearly ahead of the runner-up; otherwise `needs_review` with candidates, or `not_found`. Without a baseline it falls back to what the locator implies, and says so.
+
+Commit `.qa-mcp/baselines.json`. Do **not** commit `.qa-mcp/auth/` (saved logins); `save_login_state` adds it to `.gitignore`.
+
+## Pages behind a login and multi-step flows
+
+Every page tool accepts a `session`:
+
+```json
+{
+  "url": "https://shop.example.com/account",
+  "session": {
+    "storage_state": ".qa-mcp/auth/default.json",
+    "steps": [
+      { "action": "click", "locator": "(By.LINK_TEXT, \"My orders\")" },
+      { "action": "wait_for", "locator": "(By.CSS_SELECTOR, \"[data-testid='order-history']\")" }
+    ]
+  }
+}
+```
+
+- **`storage_state`**: cookies and localStorage saved by `save_login_state`, in the same JSON format Playwright uses. It must be inside the project.
+- **`steps`**: `goto`, `click`, `fill`, `press`, `select`, `check`, `uncheck`, `wait_for`, up to 25, with explicit waits.
+- **Secrets stay out of prompts and logs.** Write `"value": "${ENV:APP_PASSWORD}"`. Results show the placeholder; literal fill values are masked as `•••`.
+
+## Healing in CI, with an audit trail
+
+```bash
+k11-selenium-qa-mcp heal-ci --apply
+```
+
+1. Runs your pytest suite with the locator-recording plugin.
+2. For each locator failure, opens the page the test was on (logging in first if `.qa-mcp/heal.config.json` says how) and heals against the committed baseline.
+3. Applies a change only when confidence is at least **0.7** (`--min-confidence`) and clearly ahead of the runner-up. It edits every place the locator literal appears: tests, Page Objects, helpers.
+4. **Re-runs the affected tests and reverts any change whose test still fails**, keeping the others.
+5. Leaves failures that aren't about locators alone.
+6. Writes `heal-report.md` (the pull-request body) and `heal-report.json` (full evidence), plus GitHub Actions outputs.
+
+Without `--apply` it's a dry run. Copy [`docs/heal-locators.yml`](docs/heal-locators.yml) into `.github/workflows/` to run it nightly and open the pull request, and [`docs/heal.config.example.json`](docs/heal.config.example.json) to `.qa-mcp/heal.config.json`.
+
+## Install
+
+Requires Python 3.10+ and Chrome (or Edge/Firefox with `QA_MCP_BROWSER=edge|firefox`). Selenium Manager downloads the matching driver automatically.
+
+### Claude Code: plugin (recommended)
+
+Adds the MCP tools plus `/story-to-test` and `/heal-tests` (needs [uv](https://docs.astral.sh/uv/)):
+
+```text
+/plugin marketplace add K11-Software-Solutions/k11techlab-selenium-qa-mcp
+/plugin install selenium-qa@k11-selenium-qa
+```
+
+### Claude Code: MCP server only
+
+From your test project's folder:
+
+```bash
+claude mcp add selenium-qa -- uvx --from git+https://github.com/K11-Software-Solutions/k11techlab-selenium-qa-mcp k11-selenium-qa-mcp
+```
+
+Or with pip: `pip install git+https://github.com/K11-Software-Solutions/k11techlab-selenium-qa-mcp`, then `claude mcp add selenium-qa -- k11-selenium-qa-mcp`.
+
+### Claude Desktop and other MCP clients
+
+```json
+{
+  "mcpServers": {
+    "selenium-qa": {
+      "command": "uvx",
+      "args": ["--from", "git+https://github.com/K11-Software-Solutions/k11techlab-selenium-qa-mcp", "k11-selenium-qa-mcp"],
+      "env": { "QA_MCP_ROOT": "/path/to/your/tests/project" }
+    }
+  }
+}
+```
+
+The server works on the project in `QA_MCP_ROOT`, or the current directory. Tests run with the project's own interpreter: `QA_MCP_PYTHON`, else `.venv`/`venv` in the project, else the server's Python. That environment needs `pytest` and `selenium`.
+
+## Try the demo
+
+```bash
+python demo/server.py --version v1      # http://127.0.0.1:8765/login.html (alex@example.com / correct-horse)
+python demo/server.py --version v2      # the redesign
+```
+
+## Safety
+
+- **Locators are parsed, never `eval`'d.** Only `By.<STRATEGY>, "<string>"` forms (and the WebDriver strategy names) are accepted.
+- **Writes are confined to `tests/`** (`write_test`) or to the exact locator literal (`heal-ci`), which is found with Python's tokenizer, so comments and other code are never touched. Line endings are preserved.
+- **Tests run without a shell,** with the project's interpreter.
+- **Healing only suggests** in the MCP tools. `heal-ci --apply` changes code only for confident, verified fixes, and every change is in a pull request for review.
+
+## How it compares
+
+| | Runtime self-healing tools | k11 Selenium QA |
+|---|---|---|
+| Where the fix goes | Patched in memory during the run | Your source (tests and Page Objects), in a pull request |
+| Evidence | Logs | Confidence, reasons and runner-up in a report |
+| If the fix is wrong | Test passes against the wrong element | Re-run must pass, or the change is reverted |
+| Lock-in | Proxy, agent or SDK in your test run | A pytest plugin used only while healing; nothing in your code depends on it |
+
+## Development
+
+```bash
+python -m venv .venv && .venv/Scripts/pip install -e ".[dev]"   # bin/pip on macOS/Linux
+pytest        # unit, real-browser, MCP protocol and heal-ci tests (27)
+```
+
+## Roadmap
+
+- Java (JUnit 5 / TestNG) and C# (NUnit) test projects
+- Healing for chained `find_element` calls and `find_elements(...)[n]`
+- Visual (screenshot) fingerprints as an extra signal
+- PyPI release (`uvx k11-selenium-qa-mcp`)
+
+---
+
+Built by [K11 Software Solutions](https://k11softwaresolutions.com). Part of the K11 Tech Lab agentic QA series, alongside [k11 Playwright QA](https://github.com/K11-Software-Solutions/k11techlab-playwright-qa-mcp). MIT licensed.

k11_selenium_qa_mcp-0.1.0/pyproject.toml

@@ -0,0 +1,43 @@
+[build-system]
+requires = ["hatchling>=1.25"]
+build-backend = "hatchling.build"
+
+[project]
+name = "k11-selenium-qa-mcp"
+version = "0.1.0"
+description = "MCP server and Claude Code plugin for Selenium QA: verified locators, user story to pytest, and self-healing locators with an audit trail."
+readme = "README.md"
+license = "MIT"
+license-files = ["LICENSE"]
+authors = [{ name = "K11 Software Solutions" }]
+requires-python = ">=3.10"
+keywords = ["mcp", "selenium", "self-healing", "test-automation", "pytest", "claude", "qa"]
+classifiers = [
+  "Development Status :: 4 - Beta",
+  "Framework :: Pytest",
+  "Intended Audience :: Developers",
+  "Programming Language :: Python :: 3",
+  "Topic :: Software Development :: Testing",
+]
+dependencies = ["mcp>=1.20,<2", "selenium>=4.27"]
+
+[project.optional-dependencies]
+dev = ["pytest>=8", "pytest-timeout>=2"]
+
+[project.urls]
+Homepage = "https://github.com/K11-Software-Solutions/k11techlab-selenium-qa-mcp"
+Issues = "https://github.com/K11-Software-Solutions/k11techlab-selenium-qa-mcp/issues"
+
+[project.scripts]
+k11-selenium-qa-mcp = "k11_selenium_qa.cli:main"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/k11_selenium_qa"]
+
+[tool.hatch.build.targets.sdist]
+include = ["src", "README.md", "LICENSE"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+norecursedirs = ["fixtures", ".tmp*"]
+timeout = 300

k11_selenium_qa_mcp-0.1.0/src/k11_selenium_qa/__init__.py

@@ -0,0 +1,5 @@
+"""k11 Selenium QA: MCP server for Selenium test generation and self-healing locators."""
+
+from .version import VERSION
+
+__all__ = ["VERSION"]

k11_selenium_qa_mcp-0.1.0/src/k11_selenium_qa/__main__.py

@@ -0,0 +1,3 @@
+from .cli import main
+
+raise SystemExit(main())

k11_selenium_qa_mcp-0.1.0/src/k11_selenium_qa/_pytest_plugin/k11_qa_pytest_plugin.py

@@ -0,0 +1,115 @@
+"""pytest plugin loaded by k11 Selenium QA when it runs your tests (``-p k11_qa_pytest_plugin``).
+
+It records, for each failing test, the last Selenium locator that could not be found,
+the line in your code that asked for it, and the page the browser was on. Results are
+written as JSON to the path in K11_QA_RESULTS. It changes nothing about how tests run.
+Self-contained on purpose: it is put on PYTHONPATH for the project's own interpreter.
+"""
+
+from __future__ import annotations
+
+import json
+import os
+import sys
+
+import pytest
+
+_results: list[dict] = []
+_current: dict = {"file": None, "failed": None}
+
+
+def _record_failure(driver, by, value):
+    line = None
+    f = sys._getframe(2)
+    test_file = _current.get("file")
+    first_user = None
+    while f is not None:
+        fn = os.path.normcase(os.path.abspath(f.f_code.co_filename))
+        if test_file and fn == test_file:
+            line = f.f_lineno
+            break
+        if first_user is None and "site-packages" not in fn and "selenium" not in fn and "k11_qa_pytest_plugin" not in fn:
+            first_user = (fn, f.f_lineno)
+        f = f.f_back
+    try:
+        url = driver.current_url
+    except Exception:  # noqa: BLE001
+        url = None
+    _current["failed"] = {"by": by, "value": value, "line": line, "url": url,
+                          "where": f"{first_user[0]}:{first_user[1]}" if first_user else None}
+
+
+def _install() -> None:
+    try:
+        from selenium.common.exceptions import NoSuchElementException
+        from selenium.webdriver.remote.webdriver import WebDriver
+        from selenium.webdriver.remote.webelement import WebElement
+    except ImportError:
+        return
+    if getattr(WebDriver.find_element, "_k11", False):
+        return
+
+    def wrap(orig, is_driver):
+        def find_element(self, by="id", value=None):
+            try:
+                el = orig(self, by, value)
+            except NoSuchElementException:
+                _record_failure(self if is_driver else self.parent, by, value)
+                raise
+            failed = _current.get("failed")
+            if failed and failed["by"] == by and failed["value"] == value:
+                _current["failed"] = None  # found after waiting: not the cause
+            return el
+
+        find_element._k11 = True
+        return find_element
+
+    WebDriver.find_element = wrap(WebDriver.find_element, True)
+    WebElement.find_element = wrap(WebElement.find_element, False)
+
+
+_install()
+
+
+def pytest_runtest_setup(item):
+    _current["file"] = os.path.normcase(os.path.abspath(str(item.fspath)))
+    _current["failed"] = None
+
+
+@pytest.hookimpl(hookwrapper=True)
+def pytest_runtest_makereport(item, call):
+    outcome = yield
+    rep = outcome.get_result()
+    if rep.when == "call" or (rep.failed and rep.when == "setup") or (rep.skipped and rep.when == "setup"):
+        entry = {
+            "nodeid": item.nodeid,
+            "name": item.name,
+            "file": os.path.abspath(str(item.fspath)),
+            "line": (item.location[1] or 0) + 1,
+            "outcome": rep.outcome if rep.when == "call" else ("error" if rep.failed else "skipped"),
+            "duration": round(rep.duration, 3),
+        }
+        if rep.failed and call.excinfo is not None:
+            exc = call.excinfo.value
+            msg = (getattr(exc, "msg", None) or str(exc) or "").strip()
+            entry["error"] = f"{call.excinfo.typename}: {msg.splitlines()[0] if msg else ''}".strip().rstrip(":")
+            entry["errorType"] = call.excinfo.typename
+            tb = call.excinfo.traceback
+            for e in reversed(tb):
+                if os.path.normcase(os.path.abspath(str(e.path))) == _current["file"]:
+                    entry["errorLine"] = e.lineno + 1
+                    break
+            failed = _current.get("failed")
+            if failed and call.excinfo.typename in ("NoSuchElementException", "TimeoutException"):
+                entry["failingLocator"] = {"by": failed["by"], "value": failed["value"]}
+                entry["page"] = failed["url"]
+                if failed.get("line"):
+                    entry["locatorLine"] = failed["line"]
+        _results[:] = [r for r in _results if r["nodeid"] != item.nodeid] + [entry]
+
+
+def pytest_sessionfinish(session, exitstatus):
+    path = os.environ.get("K11_QA_RESULTS")
+    if path:
+        with open(path, "w", encoding="utf8") as fh:
+            json.dump({"tests": _results, "exitstatus": int(exitstatus)}, fh, indent=2)