Release date: April 17, 2020 In this release, we've focused on extending support for environments and enhancing Jtest's unit testing capabilities,. Support for IDEsWe've added support for the following IDEs:
IntelliJ 2020.1 is not currently supported. Support for Source Control Management SystemsWe've added support for:
See Deprecated Support for Environments and Systems for information about deprecated and removed support for source control management systems. Support for PlatformsWe've added support for:
Enhanced Unit TestingUnit Test Assistant Enhancements
Test Impact Analysis for JUnit 5 TestsWe've extended support for the JUnit 5 framework. You can now perform test impact analysis for JUnit 5 tests executed with Maven or Gradle. Optimized Performance for JUnit 4 and 5 Test ExecutionYou can now configure Jtest to optimize performance of test execution. This will dramatically reduce the time required to calculate results and coverage data for JUnit 4 and 5 tests, as well as help you improve the consistency of results between different versions of a build system. See Running Unit Tests for details. Extended Security Compliance PackThe Security Pack now supports CWE 4.0. In addition, we've enhanced support for CWE Top 25 2019 and On the Cusp guidelines by adding new rules and updating the existing test configurations. See New and Updated Test Configurations below for details. New Versioning ConventionAll Parasoft products, including Jtest, now follow a new versioning scheme: YYYY.release.
|
Rule ID | Header |
---|---|
BD.SECURITY.SENSLOG | Avoid passing sensitive data to functions that write to log files |
BD.SECURITY.TDALLOC | Validate potentially tainted data before it is used to determine the size of memory allocation |
SECURITY.WSC.HTTPRHA | Do not rely on IP addresses obtained from HTTP request headers for authentication |
SECURITY.WSC.JXCORS | Restrict cross-origin resource sharing to secure origins |
The following static analysis rules have been updated to improve analysis results:
BD.EXCEPT.NP
BD.PB.STRNULL
BD.SECURITY.TDRESP
BD.SECURITY.TD*
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:
Support for the following environments and systems is now deprecated and will be removed in future releases.
Support for Windows 7 is deprecated, following the system's EOL.
Support for all versions of NetBeans IDE is deprecated
Support for the following SCMs is deprecated:
In addition, we've removed support for Microsoft Team Foundation Server 2010.
Support for Java 6 and lower is deprecated. In consequence, support environments that require Java 6 or lower will be removed for future releases.
Bug/FR ID | Description |
---|---|
JT-72013 | Command Line Exit Code when the analysis scope is empty |
JT-72015 | Improve performance of global analysis |
JT-72067 | PB.CUB.UEIC false positive |
JT-72081 | EVAL - Question about results from CWE.400.DMDS |
JT-72105 | EVAL - Violations on constructor from CWE.749.DPAM |
JT-72402 | FORMAT.CBRACE potential false positive |
JT-72541 | Review problems with JUNIT.AUL and JUNIT.RPL5 |
UTA-4268 | Jtest cannot trace mock object on the attached case. |
UTA-4377 | Non-localized "Unable to detect the testing framework" message in dialog. |
UTA-4902 | No deep setup when generating Spring tests on non-handler method |
UTA-5056 | Wrong formatting and missing javadoc for Clone method action in IntelliJ. |
XT-36582 | Parasoft Plugin does not work with some versions of Eclipse and Netbeans when run with Java 11 |
XT-37673 | Static analysis run from IDE quits due to missing Command Line feature |
XT-37692 | Engine license generated by IDE can be different depends on Java or IKVM version. |
For information about this release, see https://docs.parasoft.com/display/JTEST20201/Updates+in+2020.1. |