TestWeasel 1.3
Released: 2026-01-23

Breaking changes:
- The previously opened project must be reopened once after this update.

New features:
- Enhanced iFrame detection by switching to frameLocator, allowing reliable selection by id, name, or URL (fallback). Including automatic migration of existing URL-based iFrame selectors on TestWeasel startup.
- The Custom Code editor is now expandable via drag & drop, allowing more space for editing code.

Fixed:
- Split project actions into explicit New Project and Open Project options to make project creation and opening more intuitive.
- Improved handling of corrupted settings.json: TestWeasel now falls back to the init flow instead of failing silently.
- Renaming a Weaslet now automatically updates all references in existing test cases.
-	Deleting a Weaslet resets affected test steps and marks them as soft-fail instead of breaking execution.
- Improved startup performance by introducing backend lazy loading for test suites.
- Project names are now derived exclusively from the .weasel file; the folder name no longer affects the project name.
- Introduced internal versioning for .weasel project files to ensure forward compatibility.
- Display a clear error message when opening a project with missing required Weaslets.
- Restored correct Windows path handling in __setup.ts to prevent launching Edge with an unexpected profile.
- Made the browser profile path configurable via environment variables so CI setups remain persistent across TestWeasel updates.

----------------------------------------

TestWeasel 1.2
Released: 2026-01-16

New features:
- Tags set on a test suite are now inherited virtually by child test cases (without explicit assignment), avoiding accidental tag removal.
- Added a "hidden-from-documentation" tag to exclude selected test cases or suites from the living documentation while keeping them executable.
- Introduced "skip" as a standard tag for both test suites and individual test cases.
- resolveCorrectLocator is now usable in Custom Code.
- AI-generated Custom Code now includes variables from previous test steps.
- Added a visual diff view to compare manually written Custom Code with AI-generated code.
- A warning is now displayed for suspiciously low timeout and sleep values (1-30 ms).
- Added a new menu item to open the TestWeasel installation folder.
- Improved error messages by passing through the full server response of the AI-API-Call instead of showing a generic message.

Fixed:
- Pages were rendered with an incorrect viewport size in Microsoft Edge when using a custom browser profile.
- In certain cases, manually added Custom Code conflicted with AI-generated Custom Code.
- Removed browser profile cloning to avoid security alerts and potential false malware warnings.
- Clarified the browser profile path setting to require a direct, explicit profile folder instead of the generic User Data directory.
- Tags deleted in TestWeasel were still present in the generated Playwright scripts.
- Elements inside Shadow DOMs could not be reliably interacted with (e.g. cookie banners).
- Issue where changing the ID via the number up/down control did not update the XPath in certain cases.


----------------------------------------

TestWeasel 1.1
Released: 2025-12-31

Fixed
- Fixed an issue where the Chromium browser could not be installed.
- Fixed an issue related to manual ID changes that could lead to an incorrect XPath being selected.
- Fixed an issue causing the following error:
  "Failed to execute step locator.click: clickCount: expected integer, got string"


----------------------------------------

TestWeasel 1.0
Released: 2025-12-23

Initial public release.