TAMI Studio

Appearance

TAMI Studio Release Notes ​

This is the release notes for the TAMI Studio.

INFO

The release notes uses semantic versioning:

Major updates (x.0.0) – Introduce significant changes, including potential breaking changes to existing features.

Minor updates (1.x.0) – Add new features and improvements without breaking existing functionality.

Patch updates (1.0.x) – Fix bugs and small issues without introducing new features.

v0.1.0 (BETA) ​

🚀 New Features

TAMI AI Assistant v2.0

  • Generate test cases from screenshots.
  • Document test steps from screenshots and recordings.
  • Generate test scripts from screenshots, recordings, and documented steps.
  • Diagnose test failures and provide explanations.
  • Fix missing or outdated steps in the test script based on failure diagnosis.
  • Generate bug reports based on test failure analysis.

Test Case Management

  • Create test cases, and organise by feature.
  • Document test cases with screenshots, recordings, and test steps.

Test Scripting

  • Test scripts are now linked to test cases. This means that when tests are ran, test reports are tagged to test cases, making it easier to track results on a test cases basis.
  • Access to Advanced Test Script Editor (via Test Script tab on the left navigation bar). This editor allows users to:
    • Create scripts for custom functions.
    • Add test resources such as documents or files for testing file uploads.
    • Add test data files in CSV or JSON format.

Datasets

  • Datasets are now by test-case scoped by default. It is not recommended use to project-scoped datasets.
  • Dataset properties can be declared in the test script using placeholder strings like <username> or as properties in the DATA object - these are automatically populated as entries in the Dataset panel.

Environments

  • Create an Environment to store variables and secrets specific to different deployment environments. It is recommneded to use Environments, instead of project-scoped Datasets for global test data that is related to deployment environments, such as urls.
  • Access environment variables in your test scripts using the ENV object, e.g. ENV.name, ENV.url.
  • Test runs are tagged with the selected environment, making it easy to track status by environments.

Preconditions

  • Define a test case as a precondition for another test case to reuse common logic.
  • If a precondition fails, all subsequent preconditions and the main test case are skipped. This helps tests fail fast and reduces unnecessary runs.

Jobs

  • You can schedule jobs to run tests automatically at specific times.