ATR Healer
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ATR Healerheal the failed transfer scenario using AI"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ATR Healer
ATR means Automation Test Resilience.
This project is now a local self-healing runner and MCP server for Selenide + Cucumber regression tests. It is not a VS Code extension anymore.
What It Does
Copilot / Continue / Codex
-> ATR MCP tool or ATR CLI
-> Cucumber/Selenide test run
-> failed locator + failed page HTML
-> Qwen / local fallback healer
-> safe patch under src/test/**
-> rerun test
-> Markdown reportATR is designed for Java test automation projects that use Page Objects and stable data-test-id selectors.
Related MCP server: qa-ai-mcp-server-gits
Commands
Compile ATR:
npm run compileNPM Package Usage
After ATR is published or packed, users can run it without cloning this repository:
npm install --save-dev atr-healer
npx atr --mode init
npx atr --mode mcp-config --optional-tools trueGlobal install is also possible:
npm install -g atr-healer
atr --mode init --workspace "C:\path\to\project"
atr --mode mcp-config --optional-tools trueatr --mode init copies lightweight Copilot instructions, prompts, agents, and ATR docs into the target project.
atr --mode mcp-config prints MCP configuration JSON that can be pasted into Copilot/Continue MCP settings.
Before self-healing, the target test project should have a Cucumber failure hook that writes target/failed-page.html. If it is missing, use the installed docs/atr-failure-hook.md instructions to add it under src/test/** before running ATR.
Local Coder LLM
For an internal OpenAI-compatible local coder model, use the local-coder profile. Keep private endpoints and cookies in environment variables:
$env:ATR_LOCAL_CODER_ENDPOINT = "https://<local-llm-host>/v1/chat/completions"
$env:ATR_LOCAL_CODER_COOKIE = "<cookie-name>=<cookie-value>"
atr --workspace "C:\path\to\test-project" `
--test-command ".\mvnw.cmd test" `
--feature "src/test/resources/features/example.feature" `
--scenario "Scenario name" `
--html-file "target/failed-page.html" `
--approval-mode auto-test-files `
--ai-profile local-coder `
--ai-endpoint "$env:ATR_LOCAL_CODER_ENDPOINT" `
--ai-cookie-env ATR_LOCAL_CODER_COOKIElocal-coder defaults:
provider:
openai-compatiblemodel:
ONIKStemperature:
0.6max output tokens:
163849JSON response format parameter: disabled
API call logs:
target/atr-healer/ai-logs
Run the CLI:
npm run atr -- --workspace "C:\path\to\test-project" --test-command ".\\mvnw.cmd test" --feature "src/test/resources/features/transfer.feature" --scenario "Successful transfer" --html-file "target/failed-page.html" --approval-mode auto-test-files --ai-provider openai-compatible --ai-profile alibaba-free --ai-model qwen3.7-plus --ai-endpoint "https://dashscope-intl.aliyuncs.com/compatible-mode/v1" --ai-api-key-env DASHSCOPE_API_KEYOther CLI modes:
npm run atr -- --mode knowledge --workspace "C:\path\to\project"
npm run atr -- --mode analyze --workspace "C:\path\to\project"
npm run atr -- --mode audit-test-ids --workspace "C:\path\to\project" --page Transfer --project-prefix transfer --include "src/App.jsx"Start the MCP server:
npm run mcpCurrent MCP tools:
atr_knowledge_summary
atr_analyze_project
atr_self_heal_scenarioOptional MCP tools are hidden by default. Enable them when you want Copilot/Continue to access generation-prep workflows:
$env:ATR_MCP_ENABLE_OPTIONAL_TOOLS = "true"
npm run mcpOptional tools currently include:
atr_audit_test_idsQwen Configuration
Keep the DashScope key in your environment:
$env:DASHSCOPE_API_KEY = "<your-key>"For a permanent Windows user variable:
setx DASHSCOPE_API_KEY "<your-key>"Open a new terminal after setx.
Safety
In auto-test-files mode, ATR only applies exact changes under:
src/test/**It must not patch production React source automatically. Adding or changing data-test-id attributes in UI code should be a separate reviewed change.
Docs
docs/atr-self-healing.mddocs/atr-knowledge-architecture.mddocs/codex-atr-usage.mddocs/continue-config.example.yamldocs/continue-prompts.md
Mock Project
The example project lives under:
examples/mock-banking-uiIt contains a small React page plus Selenide/Cucumber tests for demonstrating locator healing.
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for Mint — AI-powered QA that runs your app in a real browser on every PR.
Official MCP server for Qase — manage test cases, runs, suites, defects via AI tools.
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
Hosted Magento MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Related MCP Servers
- AlicenseAqualityBmaintenanceMCP server for autonomous end-to-end testing with Wopee.io. Analyzes web applications, generates and executes Playwright-based functional tests, and validates results — all driven by natural language commands.15728 npm4MIT
- AlicenseBqualityDmaintenanceMCP server for end-to-end QA automation: generates test scenarios, discovers Playwright locators, creates TypeScript test code, executes tests, and creates GitHub issues for failures.625 npmMIT
- AlicenseBqualityAmaintenancePython MCP server for Selenium WebDriver — 84 tools for browser automation, element interactions, assertions, self-healing locators, and codegen for Java TestNG / JUnit 5 / Cucumber / pytest / C# NUnit / Playwright and CI pipelines (GitHub Actions / Jenkins / GitLab CI). No ChromeDriver setup needed.85114 PyPI2MIT
- FlicenseNot gradedqualityDmaintenanceAI-driven smart browser automation MCP server supporting multiple AI providers. Enables natural language element selection and self-healing for robust web automation.-