TestNavigator 2026.4 release is here! AI Assistant, Requirements Management and Extended Jira Integration

5 min read
TestNavigator 2026.4 release is here! AI Assistant, Requirements Management and Extended Jira Integration

Discover what’s new in TestNavigator 2026.4. The latest release introduces a built-in AI assistant, AI-supported requirements management, extended Jira integration, and more powerful capabilities for external AI agents. We have also improved test case version management, code coverage measurement, and several core workflows to make testing and release preparation more efficient.

TestNavigator 2026.4 introduces new AI capabilities, requirements management and enhanced integrations. The new release brings a built-in AI assistant for accessing testing information, while FibR can extract and structure requirements directly from specification documents. Jira issue creation, test case version management and the integration of external AI agents with TestNavigator have also been improved.

AI assistant built into TestNavigator

One of the key additions in TestNavigator 2026.4 is the built-in AI assistant. Through an integrated chat interface, users can ask questions about test cases, test cycles, test executions and requirements using natural language.

The AI assistant is powered by the FabrQ agent platform. It always operates within the context of the currently selected application and follows the same access permissions as the user. This means it can only access information and perform actions that the user is authorized to access or execute.

The interface clearly indicates when AI is being used. An AI badge is displayed in the header, AI-generated responses are labeled accordingly, and an informational notice provides additional guidance on using the feature.

The AI assistant is expected to become available from September 30, 2026.

New requirements management with FibR integration

TestNavigator 2026.4 introduces a new Requirements interface designed to create a clearer connection between software specifications and testing activities.

Specification documents can be uploaded to the FibR knowledge base, where their content is analyzed and requirements are extracted automatically. The status of both document uploads and processing can be monitored directly within the system.

On the new Requirements screen, requirements can be:

  • displayed in a hierarchical structure,
  • assigned a MoSCoW priority,
  • linked to related requirements,
  • checked for identified conflicts,
  • traced back to their original source documents.

This makes it possible to turn requirements contained in lengthy specification documents into structured information that can be managed directly as part of the testing process.

FibR-based requirements management is expected to become available from September 30, 2026.

Create Jira issues directly from test executions

The Jira integration has also been extended. Jira issues can now be created directly from failed test case executions, including from multiple selected executions at once.

A new column in the execution list indicates whether an issue has already been created for a particular execution, making it easier to track defects identified during testing.

The available Test Framework options have also been expanded. In addition to Spira, Jira, Zephyr and Xray are now supported as selectable options.

New Business Analyst role

With the introduction of requirements management, TestNavigator now includes a new Business Analyst role. Business Analysts have standard user permissions as well as permission to create and edit requirements and manage specification documents.

As part of this change, some existing permissions have also been updated. Creating, editing and deleting specification documents has moved from the Configuration Manager role to the Business Analyst role. Configuration Managers and SCM users retain read access, while Software Testers can continue to view requirements but no longer have permission to modify them.

Easier test case version management in active test cycles

When editing a test case creates a new version, TestNavigator can now update active test cycles to use the new version in a single step.

During the update, the assignee, history and comments are preserved. Previous test step results, however, are removed. TestNavigator displays a system notification to make this consequence clear before the change is applied.

A new version can also be assigned to a release even if the previous version of the test case has already been executed. In addition, test case redundancy calculations are now triggered manually instead of running automatically when the corresponding tab is opened.

Extended MCP server for AI agents

The TestNavigator MCP server has been significantly expanded. External AI agents can now use 39 tools across 9 groups, compared with 13 tools previously.

This provides AI agents with access to a broader range of TestNavigator functionality, including test cycles, test executions, test case versions, baselines and source code elements that changed within a test cycle.

The release also introduces full-text search across test case content. Searches can cover not only test case titles but also descriptions, preconditions, test steps and other test case information.

Improved frontend code coverage measurement

The TypeScript Instrumenter 2.1 simplifies frontend code coverage measurement. Coverage measurement no longer requires a stop/start operation, while the current measurement state and selected environment are preserved when switching between browser tabs.

Bug fixes and additional improvements

TestNavigator 2026.4 also includes several stability and usability improvements.

Issues affecting the deletion of steps from copied test cases and the assignment of copied test cases to releases have been fixed. Baseline management has also been improved: the Remove from baseline action now works for folders, and Test Suite selectors are filtered according to the selected release.

Attachment uploads and downloads have been improved, the previously missing language field has been added, and an issue that could cause the Test Cases page to appear empty when a single Test Suite had been deleted has been resolved.

We also fixed an out-of-memory issue in production caused by the source code comparison cache. Permission handling has been refined as well: creating an application now requires write permission, and adding a test case to a test cycle requires test cycle write permission.

Updated documentation and demo video

Alongside TestNavigator 2026.4, the Hungarian and English user manuals have been updated, and a new product demo video is now available on the homepage.

The improvements introduced in TestNavigator 2026.4 are designed to bring more information and actions into a unified workflow, from requirements and test management to defect handling and release preparation.