Changelogs

TAMI StudioWeb IDETest Engine

Editor now shows file modification details

Jul 2, 2025
Web IDE

Improvements

  • Added file modification information to the editor, including the last modified time and the user who last updated the currently opened file.

Fixed Test Run Results pane behavior

May 20, 2025
Web IDE

Bug Fixes

  • Fixed an issue where the Test Run Results pane could reopen unexpectedly after being manually closed.

Improved visibility of nested preconditions

Apr 29, 2025
TAMI Studio

Improvement

  • Improved support for nested preconditions. TAMI Studio now displays preconditions of preconditions throughout the application, including the Test Steps, Dataset, and "Add/Edit Precondition" views, making it easier to understand the full dependency chain when reviewing or editing a test case.

Bug fixes

  • Fixed an issue where newly created test cases could not be run unless a dataset was selected.
  • Fixed an issue where the test case editor could load the wrong test cases after a feature was deleted and a new feature was created using the same index.

Prevent accidental edits to linked test scripts

Apr 11, 2025
Web IDETAMI Studio

Improvements

  • Test scripts linked to TAMI Studio test cases now open in read-only mode in the Script Editor. A warning banner is displayed to help prevent direct edits that could cause the script to become out of sync with its associated test case.

Improved browser edge case handling

Apr 8, 2025
Test Engine

Improvements

  • Updated I.dontSee to retry when page navigation occurs during command execution. If page navigation exceeds the page load timeout, the command will continue retrying until the configured TEST.commandTimeout is reached instead of failing early with a 504 Gateway Timeout error.

Bug Fixes

  • Fixed an issue where test commands are failing on pages with inline PDF viewers in Chromium-based browsers. This happens because the PDF viewer was detected as a new browser tab, causing the test to incorrectly switch context to the PDF viewer instead of the parent page.
  • Fixed an issue where a no such alert error could be thrown if the current page closed unexpectedly while a test command was being executed.

Introducing TAMI Studio

Mar 21, 2025
TAMI Studio

Introducing TAMI Studio, our next-generation AI-first platform for managing test cases, creating and maintaining test automation, and monitoring test execution.

Key capabilities include:

  • Test case management – Document test cases with screenshots, recordings, test steps, and automation scripts, and organize them into features.
  • AI assistant– Generate test automation scripts from screenshots and recordings, diagnose test failures, and generate bug reports.
  • Monitoring – Schedule test runs and configure email, Slack, Microsoft Teams, or webhook notifications when tests fail.

Fix test crashing on pages with inline PDF viewers

Mar 21, 2025
Test Engine

Bug Fixes

  • Fixed an issue where test crashes on pages that load an inline PDF viewer on Chromium-browsers

Fixed screenshot issues and improved Metamask setup reliability

Dec 5, 2024
Test Engine

Improvements

  • Added retries to I.switchTab until the target tab is found or the configured TEST.commandTimeout is reached.
  • Increased the timeout for the MetaMask setup flow to 60 seconds.
  • Added a fallback mechanism to detect and open the MetaMask extension when MetaMask initialisation on browser start exceeds timeout.

Bug Fixes

  • Fixed an issue where screenshots taller than 1080 pixels are not captured properly.
  • Fixed an issue where screenshots captured from the MetaMask extension could appear completely black.

Fixed file saving issues

Nov 6, 2024
Server

Bug Fixes

  • Fixed an issue where file changes made in quick succession could sometimes fail to save due to an issue with file version tracking.

Bug fixes for file saving and running jobs

Oct 18, 2024
Server

Bug Fixes

  • Fixed an issue where file changes could sometimes fail to save due to an issue with file version tracking.
  • Fixed an issue where test runs triggered by a job could fail with a "System Error" if the configured dataset for the job had been deleted. Instead of failing, the test run is now skipped.