Skip to content

30 June 2026 Release Notes

Open Source Version 5.70.2

Feature highlights

Manage your TestGen setup from AI assistants

The Model Context Protocol (MCP) server gains tools to build and manage the core pieces of a TestGen project — adding to the test definition, profiling, hygiene, run, score, schedule, and notification tools already available.

  • Create and update table groups and test suites.
  • View and test the database connection.
  • Manage monitors end to end: enable or disable them, change their settings, and review their events and schema changes.
  • Set test-result dispositions, individually or in bulk.
  • Export test definitions from one suite and import them into another.
  • View and edit Data Catalog metadata.

For the full tool reference, see Supported Tools.

Richer, more navigable test definitions

  • A new faceted picker makes adding tests faster — browse and filter the available test types as you choose.
  • Attach an external URL and custom metadata to a test definition for click-through to your own runbooks and context.
  • The Add Test and Edit Test dialogs are now organized into Parameters and Settings tabs.

Data classification tagging

Tag table groups, tables, and columns with a data classification — for example, Public, Internal, Confidential, or Restricted. Classifications appear in the Data Catalog, in scoring breakdowns, and in exports, and inherit from table group to table to column unless overridden.

REST API enhancements

  • A new endpoint returns the results of a test run.
  • Profiling and test run responses now report counts in a consistent, predictable shape.

Other fixes and enhancements

  • We improved anomaly detection on Freshness, Volume, and Metric monitors to trigger fewer false positives.
  • Azure Synapse Analytics connections can now authenticate with a Managed Identity.
  • Views are profiled more reliably on SQL Server and PostgreSQL, and the Data Catalog now shows each object's type.
  • We fixed profiling and hygiene-issue detection failing on very large tables.
  • We fixed a class of tests with empty baseline or tolerance values failing to run.
  • We improved date and time formatting across exports, schedules, PDF reports, and email notifications.
  • SQL Server schema names are now matched case-sensitively, consistent with the other databases; existing table groups whose configured schema differs only in letter case are corrected automatically on upgrade.
  • We applied general fixes to reduce errors, increase security, and improve our user experience.