This release includes the following enhancements:
Release date: May 13, 2025
In this release, the structure of the Jtest plugin for Eclipse has been significantly modified. Before installing the Jtest 2025.1 plugin, any previous versions must be uninstalled. Performing a plugin update without first uninstalling previous versions may result in Jtest functionality not working correctly. See Plugin for Eclipse. |
AI Assistant
A new AI Assistant is available in Jtest. Users can ask questions about the product in natural language and the AI Assistant will answer based on documentation and integration with an external LLM provider. New and existing users can learn the product and get help more efficiently using the AI Assistant. Access the AI Assistant by navigating in the desktop to Parasoft > Show View > AI Assistant. See The AI Assistant for more information.
Unit Test Creation Enhancements
- When LLM integration is enabled, the Unit Test Assistant now leverages LLM to provide improved variable values during test creation, such as more natural string values, in addition to the existing functionality of attempting to fix failing generated tests. These test generation enhancements can be enabled using the Use AI to enhance generated tests option.
- The Unit Test Assistant now analyzes 3rd-party libraries in user projects to understand how to better initialize objects under test in the generated test cases.
- Support for Mockito 5 has been added.
- The test suite maintainability strategy has been enhanced to create tests that are fully configured and are more likely to pass when run.
- More accurate default values are now provided for commonly used types, such as java.util.Date, java.util.Locale and java.nio.charset.Charset. Instances are now created instead of mocks for string-related types and interfaces, such as java.lang.CharSequence, java.lang.StringBuilder and java.lang.StringBuffer.
Unit Test Assistant Centralized License Token Counting
When creating tests for multiple classes at once, license tokens for test creation can now be counted centrally on the Parasoft License Server instead of locally on the individual workstation. This allows organizations to utilize the same Jtest license enabled with a Unit Test Bulk Creation Tier across multiple team members (on multiple machines). For more information, see Licensing.
Test Execution and Code Coverage Enhancements
- Code coverage analysis has been improved by excluding constructs that are not coverable:
- Private, empty, and no-argument constructors.
- Closing brackets from try-finally statements.
- Coverage can now be collected for projects using JBoss 7.3 and Java 11.
- A .yaml OpenAPI specification endpoint has been added to the coverage agent that documents the REST API exposed by the coverage agent.
- Jtest now supports collecting coverage and test results from Android Kotlin projects based on Gradle 8 and JDK 17.
Static Analysis Enhancements
The suppression mechanism has been extended to allow suppressing similar violations in different versions of Jtest.
Build and Framework Integration Enhancements
- Support for Lombok 1.18.36 has been added.
- Experimental support for Maven 4.0.0 has been added.
New and Updated Test Configurations
The Security Compliance Pack has been extended by adding support for the following test configurations:
- CWE 4.17
- CWE Top 25 2024
- CWE Top 25 + On the Cusp 2024
The following test configurations have been updated:
- Demo Configuration
- OWASP Top 10-2021
- Recommended Rules
- UL 2900
The following test configurations have been removed:
- CWE 4.15
- CWE Top 25 2022
- CWE Top 25 + On the Cusp 2022
New and Updated Static Analysis Rules
The following rule has been added:
| Rule ID | Header |
|---|---|
| SECURITY.WSC.UHTTPS | Use HTTPS instead of HTTP |
The following rules have been updated:
Rule ID | Updates |
|---|---|
| BEAN.EQUALS | Performance improved using a new framework. |
| BEAN.JDBC | Performance improved using a new framework. |
| CODSTA.BP.BLOCK | Performance improved using a new framework. |
| CODSTA.BP.CFNF | Performance improved using a new framework. |
| CODSTA.EPC.AFP | Performance improved using a new framework. |
| CODSTA.EPC.NCNFC | Performance improved using a new framework. |
| CODSTA.EPC.UST | Performance improved using a new framework. |
| CODSTA.OIM.AMMO | Performance improved using a new framework. |
| CODSTA.OIM.DVOM | Performance improved using a new framework. |
| CODSTA.POD.DCTOR | Performance improved using a new framework. |
| CODSTA.READ.DOWHILE | Performance improved using a new framework. |
| ECLIPSE.IPMF | Performance improved using a new framework. Updated the violation marker position. |
| ECLIPSE.SMF | Performance improved using a new framework. |
| EJB.ABCS | Performance improved using a new framework. |
| EJB.ABFG | Performance improved using a new framework. |
| EJB.ADCB | Performance improved using a new framework. |
| EJB.AIEBC | Performance improved using a new framework. |
| EJB.AJDBC | Performance improved using a new framework. |
| EJB.AOTO | Performance improved using a new framework. |
| EJB.EJBLOAD | Performance improved using a new framework. |
| EJB.FNDM | Performance improved using a new framework. |
| EJB.IECM | Performance improved using a new framework. |
| EJB.IEPM | Performance improved using a new framework. |
| EJB.MRE | Performance improved using a new framework. |
| EJB.RUH | Performance improved using a new framework. |
| EJB.TCE | Performance improved using a new framework. |
| EJB.TFE | Performance improved using a new framework. |
| EXCEPT.IMMEX | Performance improved using a new framework. |
| INTER.PN | Performance improved using a new framework. |
| INTER.SCT | Performance improved using a new framework. |
| INTER.SE | Performance improved using a new framework. |
| INTER.SIO | Performance improved using a new framework. |
| INTER.ST | Performance improved using a new framework. |
| JAVADOC.MVJDT | Performance improved using a new framework. |
| JUNIT.MAIN | Performance improved using a new framework. |
| MOBILE.ENUM | Performance improved using a new framework. |
| MOBILE.FLOATER | Performance improved using a new framework. |
| OOP.CIMOM | Performance improved using a new framework. |
| OOP.ICIF | Performance improved using a new framework. |
| OOP.IIN | Performance improved using a new framework. |
| OOP.LEVEL | Performance improved using a new framework. |
| OPT.BR | Performance improved using a new framework. |
| OPT.MAF | Performance improved using a new framework. |
| OPT.PCTS | Performance improved using a new framework. |
| OPT.SB | Performance improved using a new framework. |
| OPT.TOARRAY | Performance improved using a new framework. |
| OPT.USV | Performance improved using a new framework. |
| PB.API.APPG | Performance improved using a new framework. |
| PB.API.ECMC | Performance improved using a new framework. |
| PB.API.EHM | Performance improved using a new framework. |
| PB.CUB.SBC | Improved performance and documentation. |
| PB.CUB.OE | Performance improved using a new framework. |
| PB.NUM.UCM | Performance improved using a new framework. |
| PB.PCSF | Performance improved using a new framework. |
| PB.RE.NXRE | Performance improved using a new framework. |
| PB.TYPO.BW | Performance improved using a new framework. |
| PB.USC.EPC | Performance improved using a new framework. |
| PB.USC.FCBS | Improved accuracy. Fixed a false positive reported by the rule. |
| PORT.CTSP | Performance improved using a new framework. |
| PROPS.HCLS | Performance improved using a new framework. |
| SECURITY.ESD.CONSEN | Improved accuracy. Fixed a false positive reported by the rule. |
| SECURITY.WSC.FIMU | Fixed a false positive reported by the rule. |
| UC.UIMPORT | Fixed a false positive reported by the rule. |
Updated Flow Analysis Rules
The following rule has been updated:
Rule ID | Updates |
|---|---|
| BD-SECURITY-TD | The rule has been significantly updated to improve performance and accuracy. |
Support for Platforms
The following platform is now supported:
- Windows Server 2025
Support for IDEs
The following IDEs are now supported:
- Eclipse 4.34 (2024-12)
- Eclipse 4.35 (2025-03)
- IntelliJ 2024.3
- IntelliJ 2025.1
Known Limitation
In this release, the Jtest plugin on Windows may experience encoding support issues in non-English environments for IntelliJ 2024.2 and later.
VSCode Extension Enhancements
- Violations are now saved in a file when applying the Fix with AI option in Problems View.
- Authentication with Azure Pipelines no longer requires additional extensions to be installed.
- You can now import the analysis results of a project named differently than the current workspace.
- You can now import violations from GitLab to VSCode using a personal token with any role.
- It is now possible to select an AI model when working with Copilot Chat using the @parasoft participant.
Additional Updates
- The shipped JRE has been upgraded to version 21.0.7+6.
- Jtest can now be configured to be FIPS 140-3 compliant.
- Jtest now supports groups of rule equivalents. When one of these rules is suppressed at the point of violation, the suppression is automatically applied to all equivalent rules in the group. See Automatically suppress violations of equivalent rules.
- Severity is no longer ignored in suppression patterns referencing only the rule ID (e.g., PB.CUB.UEIC-3). If the rule's severity has increased, existing suppressions may no longer apply.
- You can now customize any of the intermediate XSL transformation files used to generate reports in all available formats as an alternative to building a custom XSL transformation from scratch. See Customizing XSL Files Used to Generate Reports.
- Parameters used to configure Jtest for test execution are now always included in XML reports.
- Settings can now be imported from a remote location. See Importing Preferences.
- Rule documentation is now distributed as a .zip file. You can specify the path to a .zip file containing the documentation. See Specifying the Rule Documentation Path.
- The Jtest installation process is now faster and more efficient.
- Flow Analysis performance has been improved.
Upgrade Notes
In this release, the structure of the Jtest plugin for Eclipse has been significantly modified. Before installing the Jtest 2025.1 plugin, any previous versions must be uninstalled. Performing a plugin update without first uninstalling previous versions may result in Jtest functionality not working correctly. See Plugin for Eclipse.
Deprecated Support
Deprecated Support for Operating Systems
Support for the following OS is now deprecated:
- Windows 10
Deprecated Rules
The following rules are deprecated and will be removed in future releases:
- NAMING.ID
- DBC.CPT
- DBC.IGM
- DBC.IMNR
- DBC.IPAN
- DBC.PKGC
- DBC.PKGMPOST
- DBC.PKGMPRE
- DBC.PRIC
- DBC.PRIMPOST
- DBC.PRIMPRE
- DBC.PROC
- DBC.PROMPOST
- DBC.PROMPRE
- DBC.PUBC
- DBC.PUBMPOST
- DBC.PUBMPRE
- DBC.RCC
- DBC.SYNTAX
Resolved Bugs and FRs
Bug/FR ID | Description |
|---|---|
| FA-10104 | Inconsistent results for BD-PB-CC |
| FA-10244 | BD-PB-VOVR false positive on variable updated in a loop, which is traversed only once |
| JT-77179 | Rule APSC_DV.002010.PWDPROP and APSC_DV.002530.TDCMD have different severity level in GUI, report, Test Configuration |
| JT-77142 | Jtest UC.UIMPORT rule issue |
| JT-77143 | False positive SECURITY.WSC.FIMU |
| JT-76604 | Importing Jtest Analysis Results from DTP to Visual Studio Code via JtestPlugin |
| UTA-9724 | Factory method objects may not be chosen in bulk creation |
| UTA-9726 | Misleading "Potential setup problem" |
| UTA-9793 | Exceptions because of insufficient IntentionActionImpl instances |