This release includes the following enhancements:

Release date: May 29, 2024

Test Impact Analysis Enhancements

• You can now enable continuous discovery and execution of impacted tests. Jtest will automatically notify you about test failures and changes in the covered code under development; see Test Impact Analysis.
• The test impact analysis capabilities in Jtest have been made more precise. Impacted tests are now calculated based on modified methods rather than modified classes. Additionally, code changes that do not affect the code logic no longer result in tests being detected as impacted.
• Impacted tests can now be calculated based on a wider range of methods to determine modified code, including determination of modified methods by analyzing Git commit history in addition to local modifications made in the IDE. For configuration details, see Test Impact Analysis.

Unit Test Assistant Enhancements

• Jtest introduces test templates which enable you to control the structure of test classes in order to specify common configurations that are required for your particular tests. You can configure the template for the test class and test method individually. The templates can be configured in the Unit Test Assistant preferences; see Configuring Preferences.
• The capability to create tests for modified methods has been expanded to support determination of modified methods by analyzing Git commit history in addition to local modifications made in the IDE. For configuration details, see Creating Test Suites.
• Support for @Timeout annotations in Junit 5 has been added.

OpenAI Integration

• Recommendations for Flow Analysis violations have been enhanced with OpenAI integration.
• OpenAI responses can now be translated into Chinese or Japanese; see Improving Tests with AI.

Code Coverage Enhancements

• Improved support for thread tracking in application coverage for multiuser mode.
• Performance while collecting coverage in IDE has been improved. You can now monitor coverage while executing impacted tests.

Support for Android Kotlin

• Jtest now supports test execution and collecting coverage from Android Kotlin projects.
• Jtest test impact analysis also experimentally supports Android Kotlin test execution from the command line.

Support for Java 21

Support for Java 21 has been added:

• Jtest can now analyze and test code compliant with Java 21 or earlier.
• Unit tests can be created for code compliant with Java 21 or earlier.

Security Compliance Pack Enhancements

Support for CWE version 4.14 has been added and some configurations have been updated. See the New and Updated Test Configurations section below.

Static Analysis Enhancements

• Simplified presentation of one-line Flow Analysis violations.
• The performance of several RuleWizard rules has been improved; see Updated Static Analysis Rules.
• Improvements to several rules to support Java 17 and 21 syntax; see Updated Static Analysis Rules.

New and Updated Test Configurations

The Security Compliance Pack has been extended by adding support for the following test configuration:

• CWE 4.14

The following test configurations have been updated:

• CWE Top 25 2022
• CWE Top 25 2023
• CWE Top 25 + On the Cusp 2022
• CWE Top 25 + On the Cusp 2023
• Critical Rules
• Flow Analysis Fast
• Flow Analysis Standard
• Flow Analysis Aggressive
• OWASP ASVS 4.0.3
• UL 2900
• VVSG 2.0

The following test configuration has been removed:

• CWE 4.13

Updated Static Analysis Rules

The following rules have been updated:

Updated Flow Analysis Rules

The following rules have been updated:

Support for IDEs

The following IDEs are now supported:

• IntelliJ 2023.3
• IntelliJ 2024.1
• Eclipse 2023-12 (4.30)
• Eclipse 2024-03 (4.31)

Additional Updates

• Authentication can now be enabled for connecting to a standalone License Server if it is configured to require authentication; see Setting the Parasoft License and license.network.auth.enabled.
• Support for Lombok 1.18.32 has been added.
• You can now specify custom parameters to be added to the report.xml header using the report.xml.param{n}.key and report.xml.param{n}.value settings.
• The following licensed features have been renamed:

  Old name	New name
  Unit Test Bulk Creation	Unit Test Single Class Creation
  Unit Test Tier 1	Unit Test Bulk Creation Tier 1
  Unit Test Tier 2	Unit Test Bulk Creation Tier 2
  Unit Test Tier 3	Unit Test Bulk Creation Tier 3
  Unit Test Tier 4	Unit Test Bulk Creation Tier 4

   
  Ensure the correct feature name is listed in your License settings; see jtest.license.custom_edition_features.
• The default report file names have changed for the following supported formats:

  Report Format	Before	Now
  SARIF for Azure DevOps	report.sarif	report_azure.sarif
  XSL Custom	report.html	report_custom.html

  
  For details, see Report File Names.

Known Limitations

AI recommendations generated for CDD and METRIC rules, as well as .properties and .xml files, may not be accurate and should not be relied upon. See Generating a Suggested Fix.

Removed Support

Removed Support for IDEs

Support for the following IDEs is now removed:

• IntelliJ 2020.1 - 2021.3
• Eclipse 4.8 - 4.22

As a result, Java 11 is now required for running Jtest in an IDE or as part of a build system integration. Java 1.8 is no longer compatible.

Removed Rules

Resolved Bugs and FRs