---
title: Version 2.6.0 (Aug 2026)
slug: suite-release-notes/version-260-aug-2026
docTags: 
createdAt: 2026-07-06T07:42:50.510Z
---

**Release Date: 10.08.2026**

## New Features

### Playwright Java Support

Testinium Suite now supports **Playwright with Java**, including standard Playwright Java projects as well as **Cucumber** and **Gauge** frameworks.

Playwright executions can generate **trace files** containing actions, screenshots, DOM snapshots, source information, console logs, and network requests, making it easier to investigate test failures and troubleshoot execution issues. Trace files are also automatically matched with their related scenarios in All-in-One executions when the required naming standard is followed.

[Playwright Sample Projects](https://docs.testinium.com/suite-documentation/playwright-sample-projects)

## Improvements

### UI & Visual Improvements

We’ve introduced a wide range of **UI and visual improvements across Testinium Suite**, bringing a cleaner, more consistent, and modern experience to many screens and workflows.

These updates improve overall usability, readability, and visual consistency throughout the platform. Screens that are still using the previous design will be progressively updated in upcoming releases to provide a fully unified experience.

### Security Improvement: Enhanced XSS Protection

As part of our ongoing security improvements, we have resolved a **Stored Cross-Site Scripting (XSS)** vulnerability identified during security testing.

Input validation and output handling have been strengthened to prevent potentially unsafe content from being stored and executed within the application, further improving the overall security of Testinium Suite.

## Bug Fixes

### Missing Application File Reference During Plan Execution

Fixed an issue where a test could be started from the **Plan** screen even when the required DevicePark application file reference key was missing.

The execution is now prevented in this case, and users are prompted to re-upload the related **.ipa or .apk** file before starting the test.

### Execution Termination Flow

Fixed an issue where some executions could remain stuck in the **Terminating** status. The system now validates these executions and transitions them to the appropriate final status, ensuring the termination flow completes properly.

### XML Report Parsing

Fixed an issue where whitespace differences between **test code and XML report output** could cause result parsing inconsistencies. XML report processing now handles these whitespace variations more reliably, ensuring test results are matched and evaluated correctly.