In this release, we've focused on extending Jtest's unit testing capabilities and enhancing our security compliance solution.

Support for IDEs

We've added support for the following IDEs:

• Eclipse 2019-06 (4.12)
• Eclipse 2019-09 (4.13)

Enhanced Unit Testing

Support for JUnit 5

Jtest now ships with support for JUnit 5. You can execute JUnit 5 tests and collect coverage information on the desktop and in the command line. In addition, desktop users can create and enhance JUnit 5 tests with Unit Test Assistant, as well as perform test impact analysis in Eclipse or IntelliJ IDEA.

We've added the JUnit 5 Best Practices test configuration to help you handle projects that include both JUnit 4 and JUnit 5 tests or assist you in migrating your tests from the earlier versions of the framework to JUnit 5; see Built-in Test Configurations.

Historical results associated with tests created in legacy frameworks, such as Junit 3 or JUnitParams 10.0.4, may no longer be available on DTP.

Extended Security Compliance Pack

We've added support for the latest version of Common Weaknesses Enumeration (CWE). We've added new static analysis rules and extended some existing rules to enable support for CWE 3.4, including CWE Top 25 2019 and One the Cusp guidelines; see the New and Updated Test Configurations section below.

New and Updated Test Configurations

We've added the following test configurations:

• CWE 3.4
• CWE Top 25 2019
• CWE Top 25 + On the Cusp 2019

• JUnit 4 Best Practices

• JUnit 5 Best Practices

The TDD test configuration has been renamed as "TDD Best Practices".

Removed Test Configurations

• CWE 3.2
• CWE-SANS Top 25 2011
• CWE SANS Top 25 2011 + On the Cusp
• Unit Test Assistant
• Unit Testing Best Practices

Other Changes

• We've added the -project.jsonpath option. If you you create your .json file manually (with the the -project.* options), you can configure this option to customize the default name and location of the file; see Creating Custom .json Data Files.
• We've changed the structure of coverage data files to enhance the mechanism of matching static and dynamic coverage. In consequence, Jtest no longer allows you to analyze coverage data files that were generated with earlier Jtest versions. To collect and merge coverage data, ensure that all Jtest instances thought your infrastructure have the same version. 
  
• The license.network.enabled option has been renamed as license.network.use.specified.server; see Setting the License.
• We've optimized memory usage to increase performance.

New and Updated Static Analysis Rules

The following rules have been added:

In addition, we've added a NOMCIM metric to calculate the number of method calls in methods.

The following static analysis rules have been updated to improve analysis results:

• BD.SECURITY.TDFNAMES
• CODSTA.BP.NTX
• FORMAT.CBRACE
• FORMAT.LL
• GC.OSTM
• GLOBAL.ACD
• JUNIT.AEAT
• JUNIT.ANAT
• JUNIT.ANBA
• JUNIT.ASAT
• JUNIT.ASSERT
• JUNIT.AST
• JUNIT.CBA
• JUNIT.DIR
• JUNIT.ETCTA
• JUNIT.FAIL
• JUNIT.FICB
• JUNIT.ISMTC
• JUNIT.MAIN
• JUNIT.OSIC
• JUNIT.OSUM
• JUNIT.OTDM
• JUNIT.SIA
• JUNIT.SIFN
• JUNIT.TATC
• JUNIT.TEST
• JUNIT.UPJT
• NAMING.NTEST
• PB.TYPO.EB
• SECURITY.WSC.ASAPI
• SECURITY.WSC.DMDS
• SECURITY.WSC.ICA
• SECURITY.WSC.SL
• SECURITY.WSC.STREP
• TRS.ISTART
• TRS.UCM

The severity level of the following rules has been changed:

• SECURITY.WSC.ASAPI – severity 5 has been increased to severity 3

The output messages of the following rules have been updated, and as a result, suppressions associated with these rules on DTP may no longer be available:

• BD.PB.CHECKRET

• JUNIT.AEAT

• JUNIT.ANAT

• JUNIT.ASAT

• JUNIT.FAIL
• JUNIT.OSUM
• JUNIT.OTDM
• SECURITY.WSC.ASAPI
• TRS.ISTART

Resolved Bugs and FRs