Repository navigation
Releases
Releases · K11-Software-Solutions/k11techlab-selenium-qa-mcp
k11 Selenium QA 0.2.2
Fix: heal-ci could revert a correct heal.
When a locator change kept a Page Object's size (for example "view-orders" → "show-orders") and was written within the same second as the previous test run, Python reused the old bytecode. The verification re-run then used the old locator, and the correct fix was reverted. This showed up on fast CI machines.
heal-ci now deletes the bytecode of every file it edits, and runs tests with PYTHONDONTWRITEBYTECODE=1. A regression test covers the worst case (same size, same mtime).
pip install -U k11-selenium-qa-mcpv0.2.1: correct server version
- The server now reports its own version (
0.2.1) to MCP clients and directories, instead of the MCP SDK's version.
v0.2.0: Java support
- Java projects: JUnit 5 and TestNG suites run with Maven or Gradle (or their wrappers). The project's language is detected from
pom.xml/build.gradle, or set withQA_MCP_LANGUAGE. - Java locators everywhere:
By.id(...)-style calls,@FindBy(...)(includinghow = How.X, using = "..."), andBy.toString()from Selenium exceptions. Tools return locators in the project's language. - heal-ci for Java: edits
Bycalls and@FindByannotations in tests and Page Objects, re-runs the healed tests, reverts any that still fail. For Java runs, the page is found from the locator's baseline. - Story to test: JUnit 5 or TestNG skeletons (
packageandclass_nameoptions);write_testwrites.javafiles undersrc/test/java/only. - Baselines use one canonical key, so Python and Java suites for the same app can share
.qa-mcp/baselines.json.