Skip to content

Releases

k11 Selenium QA 0.2.2

Choose a tag to compare

@kavitaj11 kavitaj11 released this 16 Nov 19:56

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-mcp

v0.2.1: correct server version

Choose a tag to compare

@kavitaj11 kavitaj11 released this 13 Nov 05:19
  • 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

Choose a tag to compare

@kavitaj11 kavitaj11 released this 13 Nov 05:09
  • 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 with QA_MCP_LANGUAGE.
  • Java locators everywhere: By.id(...)-style calls, @FindBy(...) (including how = How.X, using = "..."), and By.toString() from Selenium exceptions. Tools return locators in the project's language.
  • heal-ci for Java: edits By calls and @FindBy annotations 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 (package and class_name options); write_test writes .java files under src/test/java/ only.
  • Baselines use one canonical key, so Python and Java suites for the same app can share .qa-mcp/baselines.json.