This release includes the following enhancements:
Release date: November 5, 2025
Static Analysis Fixes Using AI Autofix
dotTEST can now autonomously fix static analysis violations that it finds within automated CI/CD pipelines. dotTEST identifies violations, uses LLM integration to propose fixes for those violations, and verifies each proposed fix to ensure that all issues are fully resolved and no new problems are introduced. Successful fixes result in automatically created commits in the working branch of your project source control repository, enabling manual review and approval before merging. See Fixing Violations Using AI Autofix.
MCP Server Extension for AI Agents
dotTEST now includes an MCP (Model Context Protocol) Server extension that enables seamless integration between dotTEST and AI agents or LLM-based coding assistants (such as GitHub Copilot). This MCP Server can be used within any LLM-enabled development environment that supports MCP integration, including Visual Studio, VS Code, and others. With this extension, an AI agent can interact directly with dotTEST, delivering context-aware guidance, analysis, and automation.
This feature allows you to use an AI coding assistant to:
- Access static analysis results to identify violations, prioritize critical issues based on your recommendations, and propose accurate fixes.
- Interpret rules and documentation, enabling you to ask targeted questions, group or prioritize rules, and more easily customize static analysis configurations, reducing manual effort and ensuring alignment with your projects' internal quality standards.
- Access information from the user guide to explain features and suggest resolutions for your issues.
- Run static analysis and access static analysis results reported to the Problems view directly from Copilot Chat in VS Code.
For details, see Configuring the MCP Server Extension for AI Agents.
Code Coverage Enhancements
- You can now report static coverage to multiple coverage images in DTP using the report.coverage.static.images option. This allows you to reuse static coverage captured during unit test execution for coverage collected from other testing practices, such as functional or manual testing — simplifying the process and reducing the amount of data sent to DTP.
- A license is no longer needed when using the coverage tools to generate static coverage images.
- When using
agent_client.exe,user input can be disabled in the command line interface after the application starts to simplify the setup in CI/CD pipelines. See nonInteractive. - Miscellaneous usability improvements have been implemented in the
agent_client.exeapplication to enhance user experience.
Static Analysis Enhancements
- Flow Analysis now understands the behavior of mathematical functions and uses it to compute results and determine more accurate constraints.
New and Updated Test Configurations
The Security Compliance Pack has been extended by adding support for the following test configurations:
- CWE 4.18
- The Common Weakness Enumeration (CWE) rule set has been extended to cover new guidelines.
- OWASP ASVS 5.0
The following test configuration has been updated:
- HIPAA
The following test configurations have been removed:
- CWE 4.16
- OWASP ASVS 4.0.3
Updated Static Analysis Rules
The following rule has been updated:
Rule ID | Updates |
|---|---|
| BRM.HBCM | Fixed false positives reported by the rule. |
Additional Updates
- Support has been added for generating LLM-based recommended fixes for static analysis violations in VB.NET.
Removed Support
Support for the following OS is now removed:
- Windows 10
Resolved Bugs and FRs
Bug/FR ID | Description |
|---|---|
| DT-22688 | User can get AI recommendations for VB.NET code |
| DT-23458 | Garbled characters in the build |
| DT-23625 | testTagFIlter is not recognizing a tag |
| DT-23928 | dotTEST 2024.2 cannot parse project though VS2022 builds it with no problem |
| DT-24029 | dotTEST was unable to analyze following projects error |
| DT-24279 | Tests in Test Explorer do not work when dotTEST is installed under VS 2017 |
| DT-24286 | Questions regarding the results with AI Autofix |
| XT-43392 | AI Assistant documentation - index out of bounds exception when no embedding model set |
| XT-43495 | Improving generating report in Visual Studio |
Resolved Bugs and FRs in 2025.2.2
Bug/FR ID | Description |
|---|---|
CVE-2026-22732 | Critical vulnerability resolved by upgrading spring-security to 6.5.9 |
CVE-2026-33937 | Critical vulnerability resolved by upgrading handlebars to 4.7.9 |
Resolved Bugs and FRs in 2025.2.3
Bug/FR ID | Description |
|---|---|
CVE-2026-29145 | Critical vulnerability resolved by upgrading Tomcat to 10.1.54 |
Resolved Bugs and FRs in 2025.2.4
Bug/FR ID | Description |
|---|---|
CVE-2026-55276 CVE-2026-53434 CVE-2026-59083 CVE-2026-59084 | Critical vulnerabilities resolved by upgrading Tomcat to 10.1.57 |
| CVE-2026-53914 | Critical vulnerability resolved by upgrading kotlin-stdlib to 2.4.20 |
Resolved Bugs and FRs in 2025.2.5
Bug/FR ID | Description |
|---|---|
| CVE-2026-8763 | Critical vulnerability resolved by upgrading bc-fips to 2.1.3 |
| CVE-2026-58062 | Critical vulnerability resolved by upgrading bc-fips to 2.1.3 |
| CVE-2026-59638 | Critical vulnerability resolved by upgrading bctls-fips to 2.1.24 |
| XT-44240 | Custom rule map did not work properly on 2025.3.x |